Two million lines have a shape
Every entry plotted by minute and by level, so the question “when did this start?” is answered by looking rather than by scrolling. Drag across a spike and the table beneath it holds only those entries.
Lives in the chart — every entry, by minute and level
The same incident, three times.
A timeline is not one picture, it is a movement: scan the day, find the hour, land on the minute. Zoom goes to 10× and pans across the range, and every step below is the same file — only the bucket width changed.
06:00 – 19:00 · 1,440 buckets
One shape stands out. You have not read a line yet.
06:55 – 07:15 · per minute
The spike has a beginning — and four minutes of nothing before it.
07:07 – 07:13 · per minute
Drag here and the table below holds only these 1,204 entries.
A gap is not a zero.
A minute with no entries at all is drawn as a break in the line. Plotting it as zero would make a service that died quietly look exactly like one that was idle — and those need completely different responses at two in the morning.
Buckets are backfilled with explicit zeroes so the chart only ever breaks where a gap was deliberately recorded.
In Live Mode this matters more: pausing records a real [pausedAt, resumedAt] interval, and the chart draws that as a break rather than pretending no data was missed while you were away.
faq
Common questions
keep reading
Where this fits
Stop scrolling to find the start.
Open a file and the timeline is already drawn. The first useful question — when did this begin? — is answered before you read a single line.