Pratik Mankawde 32d411ea25 Add Grafana Tempo as second trace backend alongside Jaeger ...

- Add Tempo 2.7.2 service to docker-compose with local storage
- Add otlp/tempo exporter to OTel Collector traces pipeline
- Add Tempo Grafana datasource provisioning with node graph
- Update 05-configuration-reference.md examples with Tempo
- OTel Collector fans traces to both Jaeger and Tempo simultaneously

Jaeger provides a standalone UI at :16686 for quick lookups.
Tempo is queryable via Grafana Explore using TraceQL and is the
recommended backend for production (supports S3/GCS storage).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-03-06 16:18:13 +00:00

..

00-tracing-fundamentals.md

Phase 1a: OpenTelemetry plan documentation

2026-02-27 17:50:27 +00:00

01-architecture-analysis.md

Phase 1a: OpenTelemetry plan documentation

2026-02-27 17:50:27 +00:00

02-design-decisions.md

Phase 1a: OpenTelemetry plan documentation

2026-02-27 17:50:27 +00:00

03-implementation-strategy.md

Phase 1a: OpenTelemetry plan documentation

2026-02-27 17:50:27 +00:00

04-code-samples.md

Phase 1a: OpenTelemetry plan documentation

2026-02-27 17:50:27 +00:00

05-configuration-reference.md

Add Grafana Tempo as second trace backend alongside Jaeger

2026-03-06 16:18:13 +00:00

06-implementation-phases.md

Phase 1a: OpenTelemetry plan documentation

2026-02-27 17:50:27 +00:00

07-observability-backends.md

Phase 1a: OpenTelemetry plan documentation

2026-02-27 17:50:27 +00:00

08-appendix.md

Phase 1a: OpenTelemetry plan documentation

2026-02-27 17:50:27 +00:00

OpenTelemetryPlan.md

Phase 1a: OpenTelemetry plan documentation

2026-02-27 17:50:27 +00:00

POC_taskList.md

Phase 1a: OpenTelemetry plan documentation

2026-02-27 17:50:27 +00:00