Timeline Analytics aggregates the phase data from every incident timeline. How long from page to ack? Ack to first action? First action to resolved? Across the whole quarter, where is the time going? Most teams find one phase that dominates, fixing it cuts MTTR more than any other change.
Every incident has four phases: page (alert fired) → ack (first responder responded) → first action (something was tried) → resolved (incident closed) → comm (status page or stakeholder update). Each phase has its own typical duration; each can become a bottleneck. The page reports p50 and p95 per phase across your incidents.
Different teams have different bottlenecks. The payments team might struggle with ack times (small team, lots of pages). The fulfillment team might have great ack but slow first actions (complex domain, sparse runbooks). The breakdown lets each team see its own dominant phase and target it.
For each phase, the page lists the slowest incidents in the window. Click any to see the timeline replay. Patterns emerge fast: same phase always slow on the same kind of incident usually points at a missing runbook or a missing tool integration.
Mark a date on the chart when you ship a fix (a new runbook, an agent that covers the class). The page draws a vertical line and computes the before/after delta on the affected phase. Use it to prove improvements rather than claim them.
Subscribe to Nova AI Ops on YouTube for demos, tutorials, and feature deep-dives.
Aggregating timelines turns "we need to be faster" into "the ack-to-first-action phase is the bottleneck, here is what to do about it."