// the find
jaegertracing/jaeger-ui
Web UI for Jaeger
The official React frontend for the Jaeger distributed tracing system. It gives you trace search, a detailed flame-graph-style timeline view, service dependency graphs, and a monitoring dashboard built on top of Prometheus metrics. If you're running Jaeger in production, this is the UI you're already using.
The trace timeline view is genuinely well-built — virtual rendering keeps it usable on traces with thousands of spans where most tools fall over. The architecture decision records in docs/adr/ are unusually good: they cover state management choices, theming strategy, and the v3 API migration with actual tradeoffs documented, not just the winning decision. Test coverage is thorough with co-located test files throughout, and the CI pipeline (CodeQL, OpenSSF Scorecard, bundle size checks) is tighter than most OSS frontends. The recent addition of a 'JaegerAssistant' AI panel shows active investment rather than maintenance mode.
The state management story is messy — there are ADRs describing both a current architecture and a target architecture that differ from each other, which means you're inheriting a codebase mid-migration and the ADRs are the only map. The dependency graph views are slow on large microservice meshes; the DAG rendering doesn't scale past ~50 services before it becomes a ball of string. The UI is tightly coupled to the Jaeger backend API — you can't point it at a generic OTLP-compatible backend without forking, which matters as the ecosystem consolidates around Grafana Tempo. The 'JaegerAsk' AI assistant is clearly experimental and ships with no documentation about what it connects to or what data it sends.