Traces (Jaeger)

https://www.jaegertracing.io/docs/next-release/getting-started/

docker run --rm --name jaeger
-e COLLECTOR_ZIPKIN_HOST_PORT=:9411
-p 16686:16686
-p 4317:4317
-p 4318:4318
-p 14250:14250
-p 14268:14268
-p 14269:14269
-p 9411:9411
jaegertracing/all-in-one:1.67.0

Jaeger UI

http://localhost:16686

Why Logs Don't Appear in Jaeger

• Jaeger is a tracing tool, designed to capture distributed traces (spans).
• It does not store or display logs (logs are a different concept in observability).
• Your logs are successfully exported via OpenTelemetry, but Jaeger ignores logs.

Where Should Logs Go?

If you want to store and analyze logs, use a log storage system like:

• Elasticsearch + Kibana (ELK Stack) → Great for search & dashboards
• Loki + Grafana → Lightweight, optimized for logs
• Application Insights / Cloud Logging (if using Azure, AWS, GCP)

Logs (Loki)

docker run --rm --name=loki -p 3100:3100 grafana/loki:latest docker run --rm --name=grafana -p 3000:3000 grafana/grafana

Needs new Package? dotnet add package OpenTelemetry.Exporter.Geneva --version 1.11.2

Add a Loki Data Source (http://localhost:3100)

• http://host.docker.internal:3100

Grafana UI

http://localhost:3000 Default User: admin Default Pw: admin

Need OpenTelemetry Collector for Loki Export

Since OpenTelemetry does not yet have a direct Loki exporter, we need to:

Use the OpenTelemetry Collector as an intermediate step. Send logs to the OpenTelemetry Collector (otel-collector). Configure otel-collector to export logs to Loki.