Claude Cursor Skill

distributed-tracing

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.

LLM Mart · 0 points · 18 views 0 listing impressions 0 install-command copies
Download wshobson-agents-plugins_observability-monitoring_skills_distributed-tracing-46891e7.zip · 4 KB

Install

skills CLI npx skills add https://github.com/wshobson/agents/tree/main/plugins/observability-monitoring/skills/distributed-tracing
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install wshobson-agents@llmmart
Git git clone https://github.com/wshobson/agents.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole wshobson/agents collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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
Files (agents)
  • references
    • details.md 7.8 KB
      Loading…
  • SKILL.md 2.1 KB
    ---
    name: distributed-tracing
    description: 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.
    ---
    
    # 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
    
    ```python
    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
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.