Jaeger: Present and Future
summary
Jaeger now collects metrics from traces by using an OpenTelemetry pipeline with a span metrics processor that generates Prometheus-compatible histograms, surfaces them in a new monitoring tab and lets Grafana or Jaeger’s metric query service run PromQL against any Prometheus-compatible backend. Deployment is managed by the Jaeger operator with three strategies (all-in-one, production, streaming), supports storages like Elasticsearch, Cassandra, Badger and Kafka, injects agents as sidecar or daemonset, deprecates native clients in favor of OpenTelemetry and ships a service performance monitoring feature and adaptive sampling roadmap.
AI-written summary · about
chapters (7)
- 0:00Start
- 20:58Tracing and Monitoring
- 21:48Aggregated Trace Metrics (ATM)
- 23:41SpanMetrics Processor in Open Telemetry
- 26:00Using Prometheus Metrics inside Jaeger UI
- 35:48New Key Features
- 36:32Roadmap
related talks
35mJaeger: The Future with OpenTelemetry and Metrics
26mJaeger V2: OpenTelemetry at the Core of Modern Distributed Tracing
41mJaeger: Intro and Deep Dive
16mGetting Started with Jaeger
37mJaeger Project Deep Dive
28mJaeger Intro and Deep Dive
33mDeploy, Scale and Extend Jaeger
37mDeep Dive: Jaeger – Steve Flanders