2 Commits

Author	SHA1	Message	Date
Pratik Mankawde	d412791a01	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-12 22:09:01 +00:00
Pratik Mankawde	d8d7a40fca	Phase 1b: Telemetry core infrastructure ... Add the OpenTelemetry telemetry library and supporting infrastructure: Build system: - Conan opentelemetry-cpp dependency with OTLP/gRPC exporter - CMake integration for xrpl_telemetry library target - Levelization ordering updates Core library (libxrpl): - Telemetry class: provider lifecycle, span creation, sampling config - SpanGuard: RAII span management with attribute/exception helpers - TelemetryConfig: parse [telemetry] config section - NullTelemetry: no-op implementation when telemetry is disabled Application integration: - Telemetry member in ApplicationImp with start/stop lifecycle - getTelemetry() interface on Application - ServiceRegistry telemetry accessor Docker observability stack: - OTel Collector, Jaeger, Grafana docker-compose setup - Collector config with OTLP gRPC receiver and Jaeger exporter Config and docs: - Example telemetry config section in xrpld-example.cfg - Build documentation for telemetry setup Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-12 22:09:01 +00:00