Description
distributed-tracing is an agent skill from the wshobson/agents collection for implementing distributed tracing with Jaeger and Tempo. Its purpose is to track requests as they move through distributed systems, so a team can see the latency, the dependencies and the failure points that a single request touches. In a microservices setup a slow response may come from any of many services, and tracing shows the path the request took and how long each step held it. The skill covers the situations where tracing is the right tool: debugging latency issues, understanding which services depend on which, identifying bottlenecks, tracing how an error propagates through the system, and analyzing request paths in general. It is meant to help an agent set up the instrumentation and backends that make traces visible, and to read the traces when a problem needs explaining. Detailed patterns and worked examples sit in a reference file, which the agent reads when the main guidance is not enough. It is installed with the skills CLI from the wshobson/agents repository. Its skills.sh page showed about 10.5K installs and passing results from three security audits at the time of the scan.…
Highlights
- Tracing with Jaeger and Tempo
- Request flow visibility across microservices
- Latency and bottleneck analysis
- Error propagation tracing
- Service dependency mapping
- Installs with the skills CLI
Ratings & Reviews
No ratings yet
Be the first to rate distributed-tracing.
People also visit
python-observability
Python observability patterns including structured logging, metrics
observability-and-instrumentation
Instruments code so production behavior is visible and diagnosable
monitoring-expert
Configures monitoring systems, implements structured logging pipelines
distributed-tracing FAQ
What does distributed tracing show?
The path a request takes across services and how long each step takes, so you can find latency and failure points.
Which tools does it use?
Jaeger and Tempo.
When is it useful?
Debugging latency, understanding service dependencies, finding bottlenecks and tracing how errors spread.
Where are the detailed examples?
In references/details.md, which the agent reads when the main guidance is not enough.
How do I install it?
Run npx skills add https://github.com/wshobson/agents --skill distributed-tracing.
What security audits does it have?
skills.sh lists three audits: Gen Agent Trust Hub Pass, Socket Pass and Snyk Pass.
What are the best distributed-tracing alternatives?
Popular alternatives to distributed-tracing include python-observability, observability-and-instrumentation and grafana-dashboards. See all distributed-tracing alternatives