observability

Implement structured logging, Prometheus metrics, OpenTelemetry tracing, and Grafana dashboards for distributed services.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/duylinhdang1998/claude-template-agent --skill observability-duylinhdang1998
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability
Source: https://github.com/duylinhdang1998/claude-template-agent/tree/main/plugins/vfm-agent-company/skills/observability
Command: npx skills add https://github.com/duylinhdang1998/claude-template-agent --skill observability-duylinhdang1998

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implement complete production observability to detect, diagnose, and resolve issues across distributed services by combining structured logs, metrics, and distributed traces so teams can reduce MTTR and monitor SLOs.

Core Features & Use Cases

  • Structured Logging: JSON request-scoped logs with correlation IDs and context to make debugging and log aggregation reliable.
  • Metrics & Dashboards: Prometheus instrumented metrics, /metrics endpoints, and Grafana dashboards for latency, error rate, and business metrics.
  • Distributed Tracing: OpenTelemetry instrumentation with Jaeger (or other exporters) to trace requests across services and identify bottlenecks.
  • Alerting & Health: Prometheus alert rules, readiness/liveness probes, and SLO-driven alerts to notify on service degradation.
  • Use Case: Add observability to an e-commerce orders service to capture request rates, p95 latency, error spikes, and end-to-end traces through payment and fulfillment flows.

Quick Start

Use the observability skill to add structured JSON logging, Prometheus metrics, OpenTelemetry tracing with Jaeger export, Grafana dashboards, and basic alert rules to the orders API.

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 for microservices using OpenTelemetry?

OpenTelemetry distributed tracing for microservices requires instrumenting code to emit spans with a Jaeger exporter to trace requests across services and identify bottlenecks.

What's the best way to set up Prometheus metrics and Grafana dashboards for an API?

Setting up Prometheus metrics for an API involves instrumenting code to expose a /metrics endpoint, then configuring Grafana dashboards to visualize latency, error rates, and business metrics for monitoring SLOs.

How do I add structured JSON logging with correlation IDs to backend services?

Structured JSON logging with correlation IDs requires implementing request-scoped logs that include context, making debugging and log aggregation reliable across distributed backend services.

Can I use this observability setup for cloud deployments and backend APIs?

Yes, this observability setup applies to backend microservices, cloud deployments, and APIs to capture request rates, p95 latency, error spikes, and end-to-end traces through payment and fulfillment flows.

How do I create SLO-based alerting and health probes for distributed services?

SLO-based alerting for distributed services requires configuring Prometheus alert rules alongside readiness and liveness probes to notify on service degradation and reduce mean time to resolution.

Why does my microservice need both metrics and distributed tracing?

Microservices need both metrics and distributed tracing because metrics monitor latency and error rates while tracing traces requests across services to identify bottlenecks, together reducing MTTR.