Vantage: an incident investigation console built for time to insight

High-density visualization that stays legible at scale

This is the heart of the piece: dense operator visuals a tired human can still read at a glance, hand-built in accessible SVG with no charting library.

Two views carry the investigation. A service topology encodes structure in shape and dependency in position, then draws one bright traced path so the eye lands on the cause instead of counting nodes. A flame graph maps width to time, so the widest bar is the answer. Both are fully keyboard navigable: nodes and spans are focusable, arrow-key reachable, and announce their selection through an ARIA live region. High information density and accessibility aren't in tension when the visual is built deliberately.

Guided analysis: surfacing the one relevant signal

Exploration tools are powerful and pitiless: infinite dimensions, and no opinion about which one matters right now.

Vantage layers guidance over raw power. Smart defaults open on the anomalous service, not the homepage. Progressive disclosure keeps the first screen to the few facts that move the investigation, with depth one interaction away. It's the "paved road" idea applied to debugging: the common path is the easy path, and the responder is steered toward the signal that explains the others instead of being handed a query builder and wished luck.

SLOs and error budgets, shown as a decision

"Is it up?" is the wrong question. The useful one is "how much room is left before we should stop shipping features and start protecting reliability?"

A service-level objective plus an error budget turns reliability from a feeling into a number a team can act on. Vantage makes that legible: a burn-down showing the budget being consumed against the safe pace, and a gauge for what remains. When an incident takes a visible bite out of the budget, the trade-off becomes a shared, explicit decision instead of an argument.

An AI that diagnoses, and a deliberate handoff before it acts

The AI panel reads the evidence and proposes a cause. It never touches production. Diagnosis and execution are split into two lanes on purpose.

Ask a plain-language question and Vantage surfaces anomalies, ranks hypotheses with honest confidence, and shows the metric, trace, and deploy evidence behind each. Then it suggests a reversible remediation, and stops. The console operates in the read lane. Anything that writes to production is handed to a human-gated control surface. That boundary is the whole safety argument: an AI's best guess earns a recommendation, never an unattended action.

One insight across UI, CLI, and API

Engineers don't live in one window. They live in terminals, IDEs, and scripts, and the answer has to read the same wherever it shows up.

The same query, "what's the slowest span in checkout?", returns the same truth as a console panel, a CLI line, and a JSON payload. That coherence is developer empathy made concrete. It respects Git and CLI-first mental models, lets the insight flow into automation, and means a finding never gets lost in translation between surfaces.

One incident, from the 3 a.m. page to the postmortem

The specimens above are stills. This is the same incident as a sequence you can click through. The page lands on the lock screen, the alert storm hands you noise with no origin, the console turns that into one cause and one suggested fix, and the postmortem drafts itself the moment a human approves. Same synthetic incident, four moments, in the order a responder lives them. Each frame below is the real app, fully interactive.