skills.rest
haxlys
haxlysCOMMUNITY
Explore all skills by this author →
GitHub

distributed-tracing

Trace requests across microservices with OpenTelemetry and Jaeger or Tempo.

1|Updated Apr 27, 2026
Search Tags:#microservices#observability#instrumentation#distributed-tracing#jaeger#tempo#trace-analysis
One-click install
npx skills add https://github.com/haxlys/skills --skill distributed-tracing-haxlys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: distributed-tracing
Source: https://github.com/haxlys/skills/tree/main/vendored/wshobson-agents/plugins/observability-monitoring/skills/distributed-tracing
Command: npx skills add https://github.com/haxlys/skills --skill distributed-tracing-haxlys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Trace requests across microservices to diagnose latency and dependency issues.

Core Features & Use Cases

  • Instrument services with OpenTelemetry to generate traces across frontend, API gateway, and backend services.
  • Visualize trace flows with Jaeger and Tempo to identify bottlenecks and error propagation.
  • Use case: isolate latency introduced by auth-service or database calls in a microservice chain.

Quick Start

Deploy Jaeger and Tempo, instrument your services with OpenTelemetry, and start tracing requests across your microservices.

Frequently Asked Questions about distributed-tracing

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

FAQPage Schema
How do I trace requests across microservices to diagnose latency?▼

To trace requests across microservices, you instrument services with OpenTelemetry and deploy Jaeger or Tempo to visualize trace flows. This end-to-end tracking isolates latency issues and identifies bottlenecks in the service chain.

How does distributed tracing identify bottlenecks in a microservice architecture?▼

Distributed tracing identifies bottlenecks by tracking context propagation across service boundaries. Visualizing trace flows with Jaeger or Tempo reveals exactly where latency is introduced, such as auth-service delays or slow database calls.

Can I use Jaeger and Tempo to visualize OpenTelemetry trace flows?▼

Yes, you can use Jaeger and Tempo to visualize OpenTelemetry trace flows. After you instrument your frontend, API gateway, and backend services, these platforms map the request paths to show error propagation and dependency issues.

What is the best way to debug latency introduced by an auth-service in microservices?▼

The best way to debug auth-service latency is using distributed tracing with OpenTelemetry. By visualizing trace flows in Jaeger or Tempo, you can isolate the specific span where the auth-service or database calls introduce delays.

Do I need OpenTelemetry instrumentation for distributed tracing across an API gateway?▼

Yes, you need OpenTelemetry instrumentation across your API gateway and backend services to generate distributed traces. This instrumentation provides the context propagation required to track requests end-to-end through Jaeger or Tempo.

Related Skills

Explore More Software Engineering Skills→
duanbiao2000duanbiao2000
3

distributed-tracing

Trace requests across microservices with OpenTelemetry and Jaeger or Tempo backends.

Community
Advanced
leonardoteodorooleonardoteodoroo

distributed-tracing

Instrument services with OpenTelemetry and configure Jaeger or Tempo for distributed tracing.

Community
Advanced
kennedym-dskennedym-ds
14

observability-telemetry

Instrument software systems with metrics, logs, and traces via OpenTelemetry, Prometheus, Grafana, and Datadog.

Community
Advanced
EngineerWithAIEngineerWithAI
4

distributed-tracing

Implement distributed tracing with Jaeger and Tempo using OpenTelemetry instrumentation.

Official
Advanced