observability

Diagnose distributed production system behavior using external telemetry signals.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/tswr/engineering-mastery-plugin --skill observability-tswr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability
Source: https://github.com/tswr/engineering-mastery-plugin/tree/main/skills/observability
Command: npx skills add https://github.com/tswr/engineering-mastery-plugin --skill observability-tswr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates blind spots in distributed production systems where traditional step-through debugging is impossible, enabling engineers to quickly diagnose issues, reduce mean time to resolution, and maintain service reliability without direct access to running code.

Core Features & Use Cases

  • Structured Logging with Correlation IDs: Implement consistent, queryable key-value log events with propagated request IDs to trace requests across services.
  • Metrics and SLO Management: Instrument the four golden signals (latency, traffic, errors, saturation) and define SLIs/SLOs with error budgets to balance feature velocity and reliability.
  • Distributed Tracing: Use OpenTelemetry to reconstruct full request causal chains across microservices for latency and error root cause analysis.
  • Alerting and Incident Response: Build symptom-based, SLO-aligned alerts with runbooks, and follow systematic debugging workflows to resolve production incidents efficiently.
  • Use Case: For a microservices e-commerce platform, use this Skill to correlate logs, metrics, and traces across order, payment, and inventory services to debug checkout failures, set latency SLOs with appropriate alerts, and conduct blameless postmortems after incidents.

Quick Start

Use the observability skill to add structured logging with correlation IDs and four golden signals metrics to your new user authentication microservice.

Frequently Asked Questions about observability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug distributed production systems when step-through debugging is unavailable?

To debug distributed production systems without step-through access, you use external telemetry signals like structured logging, time-series metrics, and distributed tracing to diagnose system behavior and reduce mean time to resolution.

What is the best way to implement structured logging with correlation IDs across microservices?

The best way to implement structured logging with correlation IDs is to generate consistent, queryable key-value log events and propagate request IDs across services to trace requests throughout the system.

How do I define SLIs and SLOs using the four golden signals metrics?

To define SLIs and SLOs using the four golden signals metrics, you instrument latency, traffic, errors, and saturation, then establish error budgets to balance feature velocity against service reliability.

Can I use OpenTelemetry distributed tracing to reconstruct full request causal chains?

Yes, you can use OpenTelemetry distributed tracing to reconstruct full request causal chains across microservices, enabling latency and error root cause analysis for complex production incidents.

How do I build SLO-aligned alerts for incident response workflows?

To build SLO-aligned alerts for incident response workflows, you create symptom-based alerts paired with runbooks and follow systematic debugging workflows to resolve production incidents efficiently.

Why do I need correlated observability data for incident debugging?

You need correlated observability data for incident debugging because it eliminates blind spots in distributed systems, providing queryable metrics, logs, and traces that directly support reliable service delivery.