observability

Distributed tracing with Jaeger, OpenTelemetry, and observability platforms for microservices insights

⭐2stars🔀0forks📁View on GitHub🕐Updated Dec 31, 2025⬇️1downloads

When & Why to Use This Skill

This Claude skill provides comprehensive support for implementing distributed tracing and observability in microservices architectures. By leveraging OpenTelemetry standards and tools like Jaeger, it helps developers manage the three pillars of observability—logs, metrics, and traces—to gain deep insights into system performance, service dependencies, and request propagation.

Use Cases

  • Microservices Troubleshooting: Trace requests across complex distributed systems to identify the root cause of latency or failures in specific service hops.
  • Performance Optimization: Use OpenTelemetry instrumentation and Jaeger visualization to map service dependencies and eliminate performance bottlenecks.
  • SRE & Reliability Engineering: Establish Service Level Objectives (SLOs) and error budgets by integrating with observability platforms like Datadog, New Relic, or Honeycomb.
  • Observability-Driven Development: Implement custom instrumentation and sampling strategies during the development phase to ensure production readiness and system transparency.
nameobservability
descriptionDistributed tracing with Jaeger, OpenTelemetry, and observability platforms for microservices insights
sasmp_version"1.3.0"
bonded_agent06-monitoring-observability
bond_typeSECONDARY_BOND

Observability Skill

MANDATORY

  • Three pillars: Logs, Metrics, Traces
  • OpenTelemetry instrumentation
  • Jaeger distributed tracing
  • Trace context propagation
  • Service dependency mapping

OPTIONAL

  • Zipkin tracing
  • New Relic APM
  • Datadog APM
  • Honeycomb observability
  • SLOs and error budgets

ADVANCED

  • Custom instrumentation
  • Sampling strategies
  • Continuous profiling
  • Chaos engineering integration
  • Observability-driven development

Assets

  • See assets/observability-config.yaml for tracing setup