distributed-tracing

Implement distributed tracing with Jaeger and Tempo for request flow visibility across microservices. Track requests across distributed systems to understand latency, dependencies, and failure points. Reference: See references/jaeger-setup.md Reference: See references/instrumentation.md Reference: See assets/jaeger-config.yaml.template Jaeger Query: Jaeger Query: Jaeger automatically generates service dependency graphs showing: No traces appearing: High latency overhead: - Debug latency issues - Understand service dependencies - Identify bottlenecks - Trace error propagation - Analyze request paths - Trace - End-to-end request journey - Span - Single operation within a trace - Context - Metadata propagated between services - Tags - Key-value pairs for filtering - Logs - Timestamped events within a span - Service relationships - Request rates - Error rates - Average latencies - Sample appropriately (1-10% in production) - Add meaningful tags (user_id, request_id) - Propagate context across all service boundaries - Log exceptions in spans - Use consistent naming for operations - Monitor tracing overhead (<1% CPU impact) - Set up alerts for trace errors - Implement distributed context (baggage) - Use span events for important milestones - Document instrumentation standards - Check collector endpoint - Verify network connectivity - Check sampling configuration - Review application...