observability-excellence

Implement OpenTelemetry tracing, JSON logging, and SLO alerting for microservices.

5|1|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/roanbrasil/engineer-grade-agent-skills --skill observability-excellence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability-excellence
Source: https://github.com/roanbrasil/engineer-grade-agent-skills/tree/main/skills/observability-excellence
Command: npx skills add https://github.com/roanbrasil/engineer-grade-agent-skills --skill observability-excellence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Without comprehensive production observability, teams struggle to debug outages, identify performance bottlenecks, and detect issues before they impact users, leading to prolonged downtime and poor user experience.

Core Features & Use Cases

  • Structured Logging, Metrics, and Distributed Tracing: Implement the three observability pillars with JSON logs, RED/USE metric strategies, and OpenTelemetry-powered distributed tracing across polyglot services.
  • SLO-Based Alerting and Dashboards: Set up symptom-driven alerts, error budget tracking, and golden signal dashboards to catch issues before users notice.
  • Production Debugging and Profiling: Use continuous profiling, error tracking with Sentry, and a step-by-step playbook to resolve slow endpoints and outages fast. For example, if your order service p99 latency spikes, use this skill to trace the slow payment call, check logs for errors, and pull a CPU profile to find the bottleneck.

Quick Start

Use the observability-excellence skill to set up structured JSON logging with correlation IDs, configure OpenTelemetry tracing for your order service, and build a golden signal dashboard for latency, traffic, errors, and saturation.

Frequently Asked Questions about observability-excellence

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

FAQPage Schema
How do I implement distributed tracing for polyglot microservices using OpenTelemetry?

Implement distributed tracing across polyglot microservices using OpenTelemetry to propagate correlation IDs, track service-to-service calls, and eliminate production blind spots in event-driven pipelines.

How do I set up SLO-based alerting and error budget burn rate tracking?

Set up SLO-based alerting by configuring error budget burn rate alerts and golden signal dashboards to track latency, traffic, errors, and saturation, catching issues before users notice.

What is the best way to structure JSON logs with correlation IDs for production debugging?

The best way to structure JSON logs is by embedding correlation IDs to connect log entries with distributed traces, enabling fast resolution of slow endpoints and outages.

Can I integrate Sentry error tracking with distributed trace context?

Yes, you can integrate Sentry error tracking with distributed trace context to capture, profile, and debug application errors alongside OpenTelemetry traces for faster root cause analysis.

How do I apply RED and USE metric labeling strategies for monitoring microservices?

Apply RED and USE metric labeling strategies to monitor microservices by tracking rate, errors, and duration for requests, alongside utilization, saturation, and errors for resources.

Does this observability approach support tail sampling for distributed traces?

Yes, this observability approach supports tail sampling for distributed traces, allowing you to reduce overhead by collecting only representative trace data from high-traffic systems.