Indent works an incident the way an on-call engineer would: gather evidence across your tools, find the root cause, then carry it straight into a fix — all in one session.
Connect your tooling
Connect the systems Indent should use during an investigation from Settings → Integrations:
- Slack — Indent reads and posts in incident channels and direct messages. See Connecting Slack.
- Datadog — Indent pulls metrics, traces, and logs. See Datadog.
- Sentry — Indent pulls error reports and stack traces. See Sentry.
- Databases — Indent runs read-only queries against PostgreSQL, BigQuery, and ClickHouse. See Connecting your database.
Start an investigation
Start from a session or from Slack. Paste a Sentry link, describe what’s happening, or mention
@indent in an incident channel.
For example:
@indent Checkout has been throwing 500s for a handful of orgs since the 2pm deploy. Sentry issue: https://acme.sentry.io/issues/44182174/
Indent pulls context from your connected systems: querying Datadog for recent metrics, checking Sentry for related errors, and running database queries to trace the issue through your data. It asks clarifying questions when it needs to — what the user was doing, whether there was a recent deploy, what the expected behavior was — then works through the evidence to a root cause.
From root cause to fix
Once Indent has a root cause, the same session can continue into a code fix. Indent already has the full investigation context, so it opens a pull request with the fix without you re-explaining the problem. See Writing code.