Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implementing observability for distributed systems.
Install with Tessl CLI
npx tessl i github:wshobson/agents --skill distributed-tracing89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Python Flask OpenTelemetry instrumentation
OpenTelemetry imports
100%
100%
BatchSpanProcessor used
100%
100%
SERVICE_NAME resource attribute
0%
100%
JaegerExporter agent host
0%
100%
JaegerExporter agent port
0%
100%
TracerProvider registration
100%
100%
FlaskInstrumentor applied
100%
100%
Context propagation inject
100%
100%
Meaningful span attributes
100%
100%
Error recording in spans
100%
100%
Manual span creation
100%
100%
Without context: $0.5987 · 9m 46s · 22 turns · 177 in / 9,301 out tokens
With context: $0.7746 · 7m 42s · 28 turns · 457 in / 7,921 out tokens
Node.js Express tracing with context propagation
OpenTelemetry packages
100%
100%
NodeTracerProvider
20%
100%
service.name resource attribute
90%
100%
JaegerExporter HTTP endpoint
100%
100%
BatchSpanProcessor used
30%
100%
provider.register() called
25%
100%
registerInstrumentations called
50%
100%
HttpInstrumentation included
87%
100%
ExpressInstrumentation included
87%
100%
Context propagation inject
100%
100%
Meaningful span attributes
100%
100%
Without context: $0.3702 · 3m 1s · 16 turns · 170 in / 5,279 out tokens
With context: $0.9569 · 8m 8s · 30 turns · 480 in / 13,155 out tokens
Docker Compose Jaeger setup with sampling and log correlation
Jaeger image
100%
100%
UI port exposed
100%
100%
Collector port exposed
100%
100%
Agent UDP port exposed
100%
100%
Zipkin port exposed
100%
100%
COLLECTOR_ZIPKIN_HOST_PORT env var
100%
100%
Probabilistic sampling rate
100%
100%
ParentBased TraceIdRatioBased sampler
0%
100%
trace_id in log records
100%
100%
trace_id 032x format
100%
100%
Without context: $0.2089 · 2m 42s · 10 turns · 81 in / 2,906 out tokens
With context: $0.3828 · 2m 57s · 17 turns · 114 in / 3,555 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.