From 718f4d1e3ca29f38d053c344f972543f2dabeb54 Mon Sep 17 00:00:00 2001 From: stxkxs Date: Tue, 23 Jun 2026 21:30:39 -0700 Subject: [PATCH] fix(dashboards): pin loki + tempo datasource UIDs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit managed-prometheus pins its UID so dashboards and alerts reference it deterministically; loki and tempo did not, so nothing could reference them by UID. Two consequences: tenant dashboards can't add a Loki logs row, and the Tempo datasource's tracesToLogsV2 bridge already references datasourceUid: loki — which resolved to nothing. Pins uid: loki and uid: tempo, fixing the trace→logs jump and unblocking logs panels. --- dashboards/base/datasources/loki.yaml | 3 +++ dashboards/base/datasources/tempo.yaml | 3 +++ 2 files changed, 6 insertions(+) diff --git a/dashboards/base/datasources/loki.yaml b/dashboards/base/datasources/loki.yaml index 57795b9..3a94111 100644 --- a/dashboards/base/datasources/loki.yaml +++ b/dashboards/base/datasources/loki.yaml @@ -8,6 +8,9 @@ spec: dashboards: external datasource: name: Loki + # Pinned UID so dashboards (tenant logs rows) and the Tempo→Loki + # tracesToLogsV2 bridge can reference this datasource deterministically. + uid: loki type: loki access: proxy url: http://loki-gateway.monitoring.svc.cluster.local diff --git a/dashboards/base/datasources/tempo.yaml b/dashboards/base/datasources/tempo.yaml index 69aac17..774fb2d 100644 --- a/dashboards/base/datasources/tempo.yaml +++ b/dashboards/base/datasources/tempo.yaml @@ -8,6 +8,9 @@ spec: dashboards: external datasource: name: Tempo + # Pinned UID so dashboards (tenant logs rows) and the Tempo→Loki + # tracesToLogsV2 bridge can reference this datasource deterministically. + uid: tempo type: tempo access: proxy url: http://tempo.monitoring.svc.cluster.local:3200