Fix Grafana TeslaMate dashboard folder provisioning #253

Merged
eblume merged 2 commits from fix/grafana-teslamate-folder into main 2026-02-22 18:38:52 -08:00
Owner

Summary

  • foldersFromFilesStructure was false in Grafana's sidecar provider config, causing Grafana to ignore the subdirectory structure the sidecar creates from grafana_folder annotations
  • All 18 TeslaMate dashboards were appearing in the root "Dashboards" folder despite having grafana_folder: "TeslaMate" annotations on their ConfigMaps
  • Flipping to true makes Grafana replicate the sidecar's directory structure as UI folders

Deployment and Testing

  • Sync grafana app: argocd app sync grafana
  • Verify TeslaMate dashboards appear under a "TeslaMate" folder in Grafana's dashboard list
  • Verify other dashboards remain in the root "Dashboards" folder
## Summary - `foldersFromFilesStructure` was `false` in Grafana's sidecar provider config, causing Grafana to ignore the subdirectory structure the sidecar creates from `grafana_folder` annotations - All 18 TeslaMate dashboards were appearing in the root "Dashboards" folder despite having `grafana_folder: "TeslaMate"` annotations on their ConfigMaps - Flipping to `true` makes Grafana replicate the sidecar's directory structure as UI folders ## Deployment and Testing - [ ] Sync `grafana` app: `argocd app sync grafana` - [ ] Verify TeslaMate dashboards appear under a "TeslaMate" folder in Grafana's dashboard list - [ ] Verify other dashboards remain in the root "Dashboards" folder
foldersFromFilesStructure was set to false, which caused Grafana's
provisioning provider to ignore the subdirectory structure created by
the sidecar's folderAnnotation feature. All dashboards ended up in the
root "Dashboards" folder despite ConfigMaps having the correct
grafana_folder annotation.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
eblume merged commit 75fde54355 into main 2026-02-22 18:38:52 -08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
eblume/blumeops!253
No description provided.