Grafana's core idea is separation: the dashboard is just a grid of panels, and each panel runs its own query against whatever data source you've wired up — Prometheus, Loki, a SQL database. That makes it the lingua franca of observability, but it also means the experience lives or dies by the query editor, which changes shape per source and assumes you can write the underlying query language. Building a panel is a tight loop of pick visualization, write query, set thresholds, watch it render. Template variables turn one dashboard into a parameterized view across hosts or services via dropdowns at the top. The dark, high-contrast default theme is built for wall-mounted screens. Polished for authors; opaque for anyone handed a dashboard without the context behind it.
Notable UX patterns
Flows
Flows for Grafana are being captured
We haven't taken Grafana apart screen by screen yet. Explore the UX patterns it's known for, or request an audit of your own product.
Request a UX auditTeardowns
Teardowns of Grafana are coming
We haven't published a written teardown of Grafana yet. Explore related topics, or request an audit.
Request a UX audit