Skip to main content
When something breaks in production, Indent can pull together the context your team needs — logs, traces, error reports, and database queries — to root-cause the issue and get to a fix faster. Best with: Slack, Datadog, Sentry, and Databases.

​
Connecting your tooling

From the Integrations page, connect the services Indent should have access to during an investigation:
  • Slack — lets your team kick off sessions by mentioning @indent directly in an incident thread or DM.
  • Datadog — pull metrics, traces, and logs to diagnose production issues.
  • Sentry — pull error reports and stack traces to debug faster.
  • Databases — connect PostgreSQL, BigQuery, Snowflake, or other databases from the Database Access page so Indent can query your data directly during an investigation.

​
Starting an investigation

You can start an investigation from chat or straight from Slack. Paste a Sentry error link, describe what’s happening, or mention @indent in an incident channel — Indent picks it up and starts working. From there, Indent pulls in context from your connected services: 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 were recent deploys, what the expected behavior was — then works through the evidence to identify a root cause.

​
From root cause to fix

Once Indent has an RCA, the same session can continue into a code fix. Because Indent already has the full investigation context — the error, the traces, the data it queried — it can open a pull request with the fix without you having to re-explain the problem. See Code for how that flow works.