Jaeger V2 - Monitoring tab now showing any data. #8129
Replies: 1 comment
-
|
You're hitting a known regression bug in v2.15.1 where the Monitor tab fails to query metrics backends even with correct configuration. This affects both Prometheus and OpenSearch backends. Quick fix: Downgrade to v2.14.1, which is the last version where the Monitor tab works correctly. Regarding your goal of on-the-fly metrics without the SpanMetrics Connector: your approach is architecturally correct! OpenSearch can calculate RED metrics directly from stored trace data upon request, eliminating the need for a separate metrics pipeline. Just ensure your extensions:
jaeger_query:
storage:
traces: opensearch_storage
metrics: opensearch_storage # or your metrics backend nameOnce you downgrade to v2.14.1, your configuration should work as expected. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I’m trying to get the “Monitor” tab to work. I’ve configured the metrics setup accordingly, but there is no data showing up.
My goal is to have the monitoring section working without the SpanMetrics Connector, with the data being calculated on the fly instead.
I’m following everything according to the official documentation, but it simply doesn’t work.
In the logs, the only relevant entry I see is:
2026-03-02T11:43:00.265Z info jaegerstorage/extension.go:241 Initializing metrics storage 'primary_store_opensearch' {"resource": {"service.instance.id": "a65178ee-ab9d-40c7-9e35-360796347c67", "service.name": "jaeger", "service.version": "v2.15.1"}, "otelcol.component.id": "jaeger_storage", "otelcol.component.kind": "extension"}Beta Was this translation helpful? Give feedback.
All reactions