AI agents are distributed systems. They fan out across LLM calls, tool invocations, memory lookups, and multi-step reasoning loops — often asynchronously. But until recently, the observability tooling hadn't caught up. You'd get logs, maybe a dashboard, but no trace of what actually happened across a full agent run. That's the gap Jaeger v2 is positioned to close — and it's not a stretch. What actually changed in Jaeger v2 Jaeger v2, released in late 2024, didn't just add features. It replaced its entire internal architecture with the OpenTelemetry Collector framework as the core foundation. What that means in practice: Native OTLP ingestion. No more translation layer from OTLP → Jaeger internal format. Telemetry flows in as-is, with no data loss from conversion. Single binary, OTel-native config. The old jaeger-agent , jaeger-collector , jaeger-ingester , jaeger-query split is gone. One binary, configured via the same YAML model as OTel Collector. Access to the full OTel Collector ecosystem.…