Problem
Two panels on the same dashboard disagree about the same number. One reads from the warehouse, one from the production replica, and nothing on the page says so, so the argument that follows is about which team is wrong rather than about which source is which.
Solution
Say where the number came from, on the panel, without being asked. A small label naming the source, its health, and ideally the query behind it.
The pattern is unglamorous and its value shows up only in specific moments, which is why it gets cut. Those moments are expensive: an incident where a source is lagging, a review where two numbers disagree, and the first week of anyone new who has no idea the company has three places a “user count” can come from.
Grafana’s model makes the need obvious. Data sources are configured objects, panels reference them by name, and a single dashboard can mix Prometheus, Loki, a SQL database and a spreadsheet in adjacent panels. Nothing about the rendered result reveals that, and the panels look equally authoritative.
There are three separable things a badge can carry, and they are worth distinguishing rather than bundling.
Identity. Which configured source this is. Cheapest, most useful, almost always sufficient.
Health. Whether that source is currently reachable and current. This overlaps with freshness and error states, and the badge is the right home for it when the panel is otherwise fine—a healthy-looking chart from a source that is twenty minutes behind is the case nothing else catches.
Derivation. What was actually asked. A link to the query, or the query itself in a popover. This is the one that ends disputes, and the one most products treat as an advanced feature.
Use when
A page mixes sources, or the same metric exists in more than one system, or the audience will act on the number without knowing the plumbing. Any executive-facing dashboard qualifies on the last point alone.
Don’t use when
Every panel on the page reads from one source and everyone knows it. Then the badge is repeated noise, and saying it once at page level is enough.
Trade-offs
Badges take space from the panel and get read only occasionally, which makes them permanently vulnerable at design review. Source names are internal and often meaningless to the audience—prom-prod-2 tells an executive nothing and might tell an engineer the wrong thing. Health indicators need their own monitoring, and a badge that shows healthy because its check is also broken is worse than no badge. And exposing the query invites people to reason about SQL they may misread, which is a real cost weighed against the disputes it settles.
Checklist
- Does the panel say which source it read from?
- Is the source name meaningful to this audience, or only to the person who configured it?
- Does the badge carry health as well as identity?
- If the source is lagging but responding, does anything on the page say so?
- Can a viewer reach the query behind the number?
- Do two panels showing the same metric from different sources make that visible?
- Is the badge redundant on a single-source page, and could it be stated once?
- Does the health check have its own failure mode, and what does the badge show then?
- Is the badge reachable by screen reader, or is it an icon with a tooltip?
- When a source is renamed or replaced, what updates the badges?
Compare
Grafana treats data sources as first-class configured objects that panels reference by name, which makes mixed-source dashboards easy to build and makes provenance entirely a matter of whether the author chose to surface it. Datadog mostly removes the question by owning ingestion, so the interesting provenance is the tag scope rather than the connector, and its UI reflects that. Honeycomb collapses source and query into one thing—you are always looking at a dataset you named in the query—so provenance is never ambiguous and never needs a badge. Looker pushes hardest in the other direction with a modelling layer, so a metric has one definition and the badge question becomes “which model version”, which is a better question and a harder one to answer in a corner of a panel.
Related
Freshness indicator answers when, where this answers where from, and the two are usually needed together. Error and stale state is what the panel shows once the source stops answering. Explain this metric covers the definition question that provenance raises. Empty state is where an unreachable source often surfaces first. Alert rule is what should notice a source going quiet before a viewer does.