Problem
People need to see when a value changed and how it behaved before and after that change.
Solution
Plot time horizontally and the measured value vertically, with clear units and a readable scale. Connect observations only when the connection accurately represents the data.
Show missing periods clearly. State the sampling or aggregation interval when it affects interpretation, especially as the selected range changes.
Choose the vertical range deliberately. A narrow range can reveal small changes but also make them look dramatic. Use consistent scales when charts are intended for direct comparison.
Use when
Timing, duration, trends, or the sequence of changes matters to the task.
Don’t use when
The categories have no natural order, or there are more series than a person can follow. Twelve lines on one chart is a legend exercise. If the answer is a distribution rather than a trajectory, a histogram or a heatmap will say more.
Trade-offs
Lines can imply continuous measurement between samples. Aggregation may hide brief spikes or outages, and averages can smooth away useful detail. Automatic scales can make small changes appear large.
Checklist
- What is the interval between points, and can the viewer tell?
- What happens to a gap: drawn as a gap, connected, or filled with zero?
- Is missing data visually distinct from a real zero?
- Does the y-axis start at zero, and if not, is that defensible for this metric?
- Does the axis rescale as data arrives, and does that make small movement look large?
- What aggregation runs when the range is wide: average, max, or last? Would max change the answer?
- Can the viewer see the time range and change it without leaving the panel?
- Where several panels share a page, do they share a time range, and a y-scale where it matters?
- Are units on the axis, and are they the units the viewer thinks in?
- How many series before this stops being readable, and what happens at that count?
Compare
Grafana exposes the gap decision as a per-panel setting with three positions, which is the most honest treatment in the category and also the reason two panels on one dashboard can disagree about the same outage. Netdata samples per second and draws it, so the chart keeps detail most tools have averaged away before it reaches the panel, at the cost of a page that never sits still. Honeycomb answers the same question with a heatmap instead of a line, arguing that a line drawn through a percentile hides the distribution that would explain it. Sentry puts the series inline on every issue row as a sparkline, the same encoding at list density, doing a job a full panel would be too expensive for.
Related
Sparkline is a compact trend beside a value. Anomaly band and Threshold line add expected ranges or limits.
Annotation places events on the timeline. Time-range picker and Zoom and pan control the period being inspected.