Narrative incidents

A narrative is the difference between "p99 is red" and "checkout is down because of the deploy four minutes ago — here's the rollback." It's the core of what Inkvo does.

How the story is built

When detection flags a deviation, Inkvo gathers the blast radius (affected services and downstream dependencies), pulls the recent change history (deploys, config, infra events), and assembles a causal chain. The narrative is the chain, written in plain English and ordered by what you need to know first.

Every claim is traceable

Narratives are grounded, not vibes. Each statement links to the trace, metric series, or deploy marker it came from. Click any colored value — a latency number, a commit SHA — to jump to the raw evidence.

Suggested actions

When Inkvo is confident about a fix it proposes one: a rollback, a config revert, or a drafted PR. Suggestions are never auto-applied — you approve them. The suggestion always explains its reasoning and its blast radius.