How it works
Connect once, then let Ketl read every alert
Point Ketl at the telemetry you already collect. The moment an alert fires, it reads across every signal, names the root cause with the evidence behind it, and proposes the exact fix or rollback.
Three steps, then it runs itself
Most teams connect their first source and run a live diagnosis in under fifteen minutes. After that, Ketl fires automatically on every alert.
Connect your telemetry
Point Ketl at the places your signal already lives: logs, traces, recent deploys, and your past incidents. No new agent to run, no data to move. Read-only by default.
ketl connect datadog pagerduty github sentryKetl reads and reasons at each alert
The moment an alert fires, Ketl pulls the relevant window across every signal and reasons about cause the way a senior on-call would, in seconds rather than an hour.
alert → reading 2,140 log lines · 3 deploys · 11 tracesYou get root cause plus a proposed fix
A ranked root cause, each with the exact lines Ketl reasoned from, and one concrete next step: a fix or a rollback, with the command and the risk. You decide, then act.
cause: N+1 from v2.48.0 · fix: rollback → v2.47.3The tools your signal already lives in
No new agent to run, no data to move. Ketl reads the sources you already run, read-only by default.
PagerDuty
AlertsTrigger a diagnosis the moment a page fires.
Datadog
Logs & metricsRead the log and metric window around an alert.
Grafana
Logs & dashboardsPull Loki logs and dashboard context.
Sentry
ErrorsAttach the exact exception and stack.
GitHub
DeploysCorrelate the alert with recent releases and PRs.
Slack
DeliveryPost the ranked cause and fix into the incident channel.
All connections are read-only by default. Ketl never writes to your systems. See the integration docs for setup guides and required permission scopes.
Root cause, evidence, and a concrete next step
Every diagnosis Ketl returns has the same three parts. Together they give you enough to act in minutes, not an hour of blind digging.
Ranked root cause
A prioritized list of likely causes, ordered by how strongly the telemetry supports each one. Each carries an honest confidence rather than a false claim of certainty.
Cited evidence
Every cause cites the exact log lines, deploy record, or past incident it reasoned from, quoted verbatim. You confirm the read or overrule it in seconds.
Proposed fix or rollback
One concrete next step for the leading cause: the exact command, the blast radius, and how to verify the fix worked. Ketl proposes; you decide; you act.
Run a diagnosis on your next alert
Start free and run a real diagnosis before you connect anything. Paste an alert and its logs, and Ketl returns a ranked root cause with evidence and a proposed fix.