observability

Correlate structured logs, metrics, and distributed traces for production monitoring.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Samuelca6399/AbsolutelySkilled --skill observability-samuelca6399
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: observability
Source: https://github.com/Samuelca6399/AbsolutelySkilled/tree/main/skills/observability
Command: npx skills add https://github.com/Samuelca6399/AbsolutelySkilled --skill observability-samuelca6399

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Observability helps teams understand system behavior from outside by correlating logs, metrics, and distributed traces so they can detect issues early and debug quickly.

Core Features & Use Cases

  • Structured logging: Produce consistent, queryable machine-readable logs with correlation identifiers for end-to-end traceability.
  • Metrics for SLOs and alerting: Instrument the right quantities (utilization/saturation/errors vs rate/duration/errors) and define SLIs/SLOs with actionable error budgets.
  • Distributed tracing with context propagation: Implement OpenTelemetry-based tracing across service boundaries so slow requests and failures can be attributed to where time is spent.
  • Dashboards and alert hygiene: Use RED-style dashboard layouts and design multi-window burn-rate alerts to reduce alert fatigue.

Quick Start

Use the observability skill to guide your setup of structured JSON logs, OpenTelemetry instrumentation (including traceparent propagation), and SLO-driven alerting for a Node.js service.

Frequently Asked Questions about observability

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

FAQPage Schema
How do I implement distributed tracing and context propagation across async boundaries using OpenTelemetry?▼

Distributed tracing with OpenTelemetry instruments services to propagate trace context, including traceparent headers, across async boundaries so slow requests and failures can be accurately attributed to specific service components.

How do I set up SLO error budgets and burn-rate alerting rules in Prometheus?▼

SLO error budgets define actionable thresholds for service reliability, allowing you to configure multi-window burn-rate alert rules in Prometheus to detect rapid error budget consumption and reduce alert fatigue.

What is structured logging and how do I add trace IDs for log correlation?▼

Structured logging produces consistent, queryable JSON logs with correlation identifiers like trace IDs, enabling end-to-end traceability across distributed services for faster production debugging.

What is the best way to design Grafana dashboards to monitor service RED metrics?▼

Designing Grafana dashboards using RED-style layouts monitors rate, errors, and duration metrics, providing actionable visibility into service performance and helping detect utilization and saturation issues early.

Can I use this observability instrumentation for a Node.js service with OTLP exporters?▼

Yes, this observability setup supports Node.js services by configuring OpenTelemetry instrumentation with OTLP exporters to send spans and metrics to compatible backends for comprehensive monitoring.

Why do I need both metrics and traces to diagnose production incidents?▼

Metrics quantify system health through SLIs and error budgets while traces attribute latency and failures to specific code paths, together providing correlated context needed to prevent production incidents.