Index of every page on this site: llms.txt
All skills
wshobson avatar

/distributed-tracing

@4220308
by Seth Hobsonwshobson/agents43k stars
4,518
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/wshobson/agents/distributed-tracing

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈66 tokens for metadata: the name and description. ≈454 when used: this file. ≈2k more on demand in 1 file.

Description uses 3.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈264 characters, or 3.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Distributed Tracing

Implement distributed tracing with Jaeger and Tempo for request flow visibility across microservices.

Purpose

Track requests across distributed systems to understand latency, dependencies, and failure points.

When to Use

  • Debug latency issues
  • Understand service dependencies
  • Identify bottlenecks
  • Trace error propagation
  • Analyze request paths

Detailed patterns and worked examples

Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.

Best Practices

  1. Sample appropriately (1-10% in production)
  2. Add meaningful tags (user_id, request_id)
  3. Propagate context across all service boundaries
  4. Log exceptions in spans
  5. Use consistent naming for operations
  6. Monitor tracing overhead (<1% CPU impact)
  7. Set up alerts for trace errors
  8. Implement distributed context (baggage)
  9. Use span events for important milestones
  10. Document instrumentation standards

Integration with Logging

Correlated Logs

import logging
from opentelemetry import trace

logger = logging.getLogger(__name__)

def process_request():
    span = trace.get_current_span()
    trace_id = span.get_span_context().trace_id

    logger.info(
        "Processing request",
        extra={"trace_id": format(trace_id, '032x')}
    )

Troubleshooting

No traces appearing:

  • Check collector endpoint
  • Verify network connectivity
  • Check sampling configuration
  • Review application logs

High latency overhead:

  • Reduce sampling rate
  • Use batch span processor
  • Check exporter configuration

Related Skills

  • prometheus-configuration - For metrics
  • grafana-dashboards - For visualization
  • slo-implementation - For latency SLOs

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts1mo5 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    This skill provides standard patterns and configurations for implementing distributed tracing using Jaeger and Tempo. It includes Kubernetes deployment manifests and application instrumentation examples for Python, Node.js, and Go using official OpenTelemetry libraries. No security issues were detected.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

  • Runlayer8mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 4220308. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 6 months ago
  • distributed-tracing
  • jaeger
  • tempo
  • microservices
  • observability
  • opentelemetry
  • instrumentation
  • performance-debugging

README badge

README badge for wshobson/agents/distributed-tracing

Implement distributed tracing with Jaeger and Tempo to track requests across microservices, identify latency issues, and understand service dependencies. The skill covers span instrumentation, context propagation, sampling strategies, and integration with logging to correlate traces with application logs.

Generated from the current SKILL.md.

Does this skill cover both Jaeger and Tempo?
Yes. The skill provides patterns for implementing distributed tracing with either Jaeger or Tempo to track requests across microservices.
What sampling rate should I use in production?
The skill recommends sampling 1-10% of traces in production to balance observability with overhead.
How do I correlate traces with logs?
The skill includes a Python example showing how to extract the trace_id from the current span and add it to log output for correlation.
What should I do if traces aren't appearing?
Check the collector endpoint, verify network connectivity, review sampling configuration, and examine application logs for errors.
How much CPU overhead should distributed tracing have?
The skill recommends monitoring to keep tracing overhead below 1% CPU impact in production.

Generated from the current SKILL.md. These answers refresh after source changes.