Skip to content

fix(dashboards): pin loki + tempo datasource UIDs#67

Merged
stxkxs merged 1 commit into
mainfrom
pin-loki-tempo-uids
Jun 24, 2026
Merged

fix(dashboards): pin loki + tempo datasource UIDs#67
stxkxs merged 1 commit into
mainfrom
pin-loki-tempo-uids

Conversation

@stxkxs

@stxkxs stxkxs commented Jun 24, 2026

Copy link
Copy Markdown
Member

managed-prometheus pins its UID so dashboards/alerts reference it deterministically; loki + tempo did not, so nothing could reference them by UID — tenant dashboards can't add a Loki logs row, and the Tempo datasource's tracesToLogsV2 already references datasourceUid: loki which resolved to nothing. Pins uid: loki + uid: tempo, fixing the trace→logs jump and unblocking tenant logs panels. yamllint + overlays build clean.

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.
@github-actions

Copy link
Copy Markdown

CI Results

Check Status
YAML Lint
Environment Kustomize Build
dev
staging
production
hub

All validations passed.

@stxkxs stxkxs merged commit 46c861c into main Jun 24, 2026
8 checks passed
@stxkxs stxkxs deleted the pin-loki-tempo-uids branch June 24, 2026 04:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant