Repository navigation
fix(grafana): keep MySQL-only dashboards out of PostgreSQL deployments - #9408
Open
KennethWKZ wants to merge 1 commit into
Open
KennethWKZ wants to merge 1 commit into
KennethWKZ wants to merge 1 commit into
Conversation
ClaudeCodeAdoption, ClaudeCodeAdoptionByUser, Incidentio, Linear and Rootly sat at the root of grafana/dashboards, so the image provisioned them in both database modes. They query the MySQL datasource, so on PostgreSQL they showed up as broken dashboards. Move them to grafana/dashboards/mysql, where the entrypoint already keeps only the folder for the configured database. The grafana smoke test now also fails when a provisioned dashboard points at the other database's datasource.
KennethWKZ
force-pushed
the
fix/grafana-db-specific-dashboards
branch
from
November 19, 2026 03:05
3b8daf4 to
4072d5b
Compare
klesh
approved these changes
Nov 19, 2026
klesh
left a comment
Contributor
There was a problem hiding this comment.
Good catch.
Thanks for your conribution.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Five dashboards sit at the root of
grafana/dashboardsbut query only the MySQL datasource: Claude Code Adoption, Claude Code Adoption by User, incident.io, Linear and Rootly. Because they are at the root, thedevlake-dashboardimage provisions them in both database modes, so a PostgreSQL deployment shows them as broken dashboards.This PR moves them to
grafana/dashboards/mysql, where the entrypoint already keeps only the folder for the configured database. Their content is unchanged.It also extends
grafana/scripts/smoke-test.sh: the test now fails when a provisioned dashboard points at the other database's datasource, so a dashboard added at the root for one database is caught in CI.Does this close any open issues?
No open issue. Found on a PostgreSQL deployment: incident.io was provisioned and broken (its datasource is written as plain
mysql), and the other four only stayed out because of a local workaround.Screenshots
Not applicable (file moves and a test change).
Other Information
Tested:
grafana/scripts/smoke-test.shpasses in PostgreSQL mode and in MySQL mode with the moved files.dashboards for another database are provisioned in postgresql mode: /etc/grafana/dashboards/Linear.json.Suggested label:
pr-type/bug-fix.