Search before asking
Use case
As an engineering lead on a non-English-speaking team, I want the DevLake dashboards (Four Keys, DORA, etc.) to support localized panel titles and labels, so that stakeholders who are not fluent in English can read metrics like Deployment Frequency or Lead Time for Changes without a mental translation step.
Description
Grafana itself supports UI localization via user Preferences (the menu, buttons, and other chrome can be switched to another language), but this only affects Grafana's own UI shell. The dashboards DevLake ships (Four Keys, DORA, DORA Details - *, etc.) are provisioned as static JSON with English panel titles, axis labels, and legend text hardcoded into the JSON. Switching Grafana's Preferences → Language does not change any of that content, so a non-English team still sees an all-English dashboard.
Possible directions (not mutually exclusive):
- Ship localized JSON variants of the built-in dashboards (e.g. one folder per locale) that users can opt into via config-ui or an env var, similar to how some BI tools ship translated report packs.
- Support templating panel titles from a small key→string map per locale, so a fork only needs to maintain a translation file instead of a full dashboard JSON copy (which then drifts from upstream on every dashboard update).
- At minimum, document a supported/low-friction way to fork+translate a shipped dashboard's JSON without losing the ability to pull future upstream changes into it.
I don't have a strong opinion on which direction is best, but I'm willing to help prototype one (see below) if a maintainer can point at the preferred approach.
Related issues
None found.
Are you willing to submit a PR?
Code of Conduct
Search before asking
Use case
As an engineering lead on a non-English-speaking team, I want the DevLake dashboards (Four Keys, DORA, etc.) to support localized panel titles and labels, so that stakeholders who are not fluent in English can read metrics like Deployment Frequency or Lead Time for Changes without a mental translation step.
Description
Grafana itself supports UI localization via user Preferences (the menu, buttons, and other chrome can be switched to another language), but this only affects Grafana's own UI shell. The dashboards DevLake ships (Four Keys, DORA, DORA Details - *, etc.) are provisioned as static JSON with English panel titles, axis labels, and legend text hardcoded into the JSON. Switching Grafana's Preferences → Language does not change any of that content, so a non-English team still sees an all-English dashboard.
Possible directions (not mutually exclusive):
I don't have a strong opinion on which direction is best, but I'm willing to help prototype one (see below) if a maintainer can point at the preferred approach.
Related issues
None found.
Are you willing to submit a PR?
Code of Conduct