Case study
Kibana Dashboard Migration and Localization for IT Services
How SquareShift translated 50-plus Kibana dashboards into 10 languages while migrating a global IT services provider from Elastic 7.17 to 8.5.
A global IT infrastructure services provider operating across Asia, Europe, and the Americas.
Its analytics and observability platform supports large-scale system monitoring and incident analysis for internal teams working in multiple languages.
Kibana dashboards translated and migrated. Languages supported across localized dashboards. Delivered across Elastic 7.17 and 8.5 simultaneously.
Key servicesHow SquareShift delivered it.
The challenge
The client, a global IT infrastructure services provider spanning Asia, Europe, and the Americas, ran its system monitoring and incident analysis on Kibana dashboards — but its internal teams needed that analytics platform in more than 10 languages. Kibana’s built-in internationalization covers the interface itself, not the custom panel labels and text blocks the client had built.
An in-flight Elastic upgrade from 7.17 to 8.5 added a second constraint: the localization solution had to work across both versions, and data privacy rules meant the translation work couldn’t leave the client’s own infrastructure.
What we delivered
SquareShift built a secure, in-house translation service that combined Azure Translator with the Kibana API, automating the fetch, translation, and re-upload of dashboard content end to end.
The team rolled the solution out in two phases to cover both Elastic 7.17 and 8.5, translated more than 50 dashboards — including custom visualizations and every field type — and validated the full pipeline inside the client’s own environment.
The payoff
More than 50 Kibana dashboards now run in over 10 languages, giving the client’s global teams the same monitoring and incident-analysis views in their own language. The translation pipeline runs entirely within the client’s infrastructure, so no dashboard content or data privacy commitment was compromised to get there.
Kibana's built-in localization stops at the UI chrome — every custom panel label needs its own pipeline, especially when the data can't leave the client's infrastructure.
Platform & Software Engineering Practice Lead, SquareShift
Where this work sits
