.svg)
Query the tools your team uses to help investigate an incident, generate a timeline, or keep your stakeholders up to date, all without ever having to leave your incident channel.
Rootly AI has always been able to reason with the data inside Rootly to help respond to incidents: alerts, past incidents, and retrospectives. Now, AI Connectors extend that reach to your third-party sources in real time. Ask a question with @Rootly, and it will gather live evidence from your observability, code, infrastructure, feature flag, ticketing, and documentation platforms alongside your incident data to support your investigation.
Use Rootly's AI Agent, powered with AI Connectors, to answer questions like:
- What are the logs showing since the incident was detected?
- Which PR's have shipped right before the incident started? Include a link and the test results.
- Which LaunchDarkly feature flags were gating this feature? Which customers have access to that feature?
- What's the EC2 and RDS state in AWS?
- What's the next step in the runbook for this kind of incident?
Answering "what changed right before this broke?" usually means an engineer hopping across half a dozen tabs. With AI Connectors, Rootly AI does that gathering itself and hands the responder the evidence in one place, with every conclusion linked back to queries the engineer can open and re-run.
What's included
- One-click OAuth connectors: Sentry, GitHub, Atlassian (Jira and Confluence), Notion, Linear, LaunchDarkly, Braintrust, and Cloudflare (fourteen surfaces including DNS, Workers, Zero Trust, and Radar)
- Short setup: AWS (IAM Role via CloudFormation, Terraform, or manual, with optional EKS), Datadog, Grafana Cloud, Grafana Managed, New Relic, and Semaphore
- Custom connectors: point Rootly AI at any OAuth-based MCP endpoint with an allowlist of tools it can call
Every connection is read-only, with no exceptions. Rootly AI queries at investigation time only, never on a schedule, and doesn't keep a copy of the underlying data. Credentials are stored encrypted.
Why it matters
Cross-tool investigation knowledge tends to concentrate in a few senior engineers, and incidents pull them in no matter who is on call. When Rootly AI gathers the diff, the flag audit history, and the infrastructure state itself, more incidents resolve with the first responder, and the engineer holding the pager at 3 AM starts from the same evidence a staff engineer would have assembled.
Set up connectors in AI Connectors. Full setup guides in the docs.
