Teams need to discuss specific chart data and keep their findings attached to it.
Updated September 10, 2026
Problem
Discussions about a chart can lose their meaning when the exact point or time range is not recorded with them.
Solution
Attach comments to a specific panel, point, or time range. Preserve enough context for someone returning later to understand what was discussed.
Distinguish a conversation that needs a reply from a note meant to record a finding. Support notifications and resolution for discussion, and keep lasting notes easy to find without covering the chart.
Show when changes to a panel have made an old comment’s reference unclear. Link to the relevant detail or saved view where possible.
Use when
A team returns to the same charts and needs to preserve findings or discuss specific data.
Don’t use when
The conversation belongs somewhere with a workflow—an incident record, a ticket—and a comment on a panel would fragment it. Dashboards are a poor system of record and a good place to point at one.
Trade-offs
Comments accumulate and can clutter the dashboard. Discussion may be split between the chart and other messaging tools. Changes to panels or live data can make old comments misleading unless their original context is preserved.
Checklist
What is a comment anchored to: dashboard, panel, time range, or point?
Does the anchor survive the panel being edited or moved?
Is this a message to someone now, or a record for later, and does the UI distinguish them?
Can a resolved conversation be cleared without losing the finding?
Is there notification, and does it create an inbox nobody wanted?
Can a comment be found later by searching, or only by returning to the panel?
Does the comment carry the state it was made against, including filters?
Who can see comments, and does that match who can see the data?
What happens to comments when the dashboard is duplicated?
Is anything pruning notes nobody has read in two years?
Compare
Grafana has no comment system and expects the annotation mechanism to carry it: a stored annotation has a text field and tags, so a note is an event with prose attached, which anchors to time reliably and has no notion of conversation. Datadog has notebooks and per-graph discussion, keeping the analysis and the commentary in one artefact, which is closer to the record use than the message use. Notion and Figma are the reference implementations for anchored commenting generally, and dashboards have borrowed the interaction without borrowing the resolution model that keeps it from accumulating. Incident tools solve the record half properly by making the timeline the artefact and the dashboard a link into it, which is usually the better division of labour.
Related
Annotation marks recorded events. Share and embed provides ways to send a view to others. Saved view preserves a useful dashboard state.
Auto-insight adds machine-generated findings. Drill-down links a note to more specific evidence.
Wireframe — the pattern's anatomy, not any one product's version of it
Implementation
Two people looking at the same spike, talking about it in place. A comment anchored to a timestamp survives the conversation; the same words in a chat thread are unfindable a month later.