> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rootly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connectors

> Connect the SaaS tools your team already uses — observability, code, docs, work tracking, feature flags, and cloud infrastructure — as data sources Rootly AI can query during investigations.

## Overview

Rootly AI is only as good as the context it can reach. **Connectors** link the SaaS tools your team already uses — observability platforms, code hosts, documentation systems, work trackers, feature-flag services, and cloud infrastructure — so Rootly AI can pull real context from them while investigating an incident, summarizing a timeline, or answering an operational question.

When an investigation runs, Rootly AI looks up just the context it needs from each connected tool and reasons over the results alongside the incident record. Every connection is **read-only** — Rootly AI can query these tools but never modify them.

***

## How Rootly AI Uses Connectors

Each connected tool gives Rootly AI a different kind of signal.

| Category                                                                                                                | What Rootly AI gets                                                                                                                             |
| ----------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| **Observability** — Sentry, Datadog, Grafana Cloud, Grafana Managed, New Relic, Braintrust, several Cloudflare surfaces | Errors, stack traces, metrics, logs, traces, dashboards, alerts. Answers *"what is broken and how bad is it?"*                                  |
| **Code & CI/CD** — GitHub, Semaphore                                                                                    | Recent deploys, code diffs, file ownership, pipeline health. Answers *"what changed right before this broke?"*                                  |
| **Infrastructure** — AWS, Cloudflare                                                                                    | CloudWatch metrics, EC2 and RDS state, DNS, Workers, Zero Trust posture. Answers *"what's the current state of the underlying infrastructure?"* |
| **Feature flags** — LaunchDarkly                                                                                        | Flag targeting, recent flag changes, audit history. Answers *"did a flag flip cause this?"*                                                     |
| **Work tracking** — Atlassian (Jira), Linear                                                                            | Related issues, project context, ownership. Answers *"who owns this and what work is already in-flight?"*                                       |
| **Knowledge** — Notion, Atlassian (Confluence)                                                                          | Runbooks, architecture docs, past decisions. Answers *"how are we supposed to fix this?"*                                                       |
| **Custom** — Any OAuth MCP server                                                                                       | Your own MCP endpoint plus an allowlist of tools. Covers anything not in the built-in catalog.                                                  |

<Note>
  **Connectors vs. other integration surfaces**

  * **[Alert Sources](/alerts/alerts)** — when your monitoring fires, an incident lands in Rootly. Data flows monitoring → Rootly.
  * **Regular Integrations** — Rootly posts to Slack, creates Jira tickets, pages on-call. Data flows Rootly → tool.
  * **Connectors** — Rootly AI looks up context in your tools while investigating. Data flows tool → Rootly AI, only during an investigation.

  A single vendor can appear in more than one surface. Datadog, for example, can be an Alert Source (ingesting Datadog alerts as Rootly alerts) *and* a Connector (letting Rootly AI read Datadog logs during investigation). The two configurations are separate.
</Note>

***

## Provider Directory

Configure connectors in **Configuration → AI → Connectors**. Each provider connects through one of two setup flows — one-click for vendors that support it, or a short configuration form for vendors that need instance URLs, API keys, or IAM roles.

### One-Click Providers

Click **Connect** on the provider card, sign in on the vendor's authorization screen, and you're done. No fields to fill in.

| Provider                                    | Category                       | What Rootly AI gets                                                                                       |
| ------------------------------------------- | ------------------------------ | --------------------------------------------------------------------------------------------------------- |
| **Sentry**                                  | Observability                  | Errors, stack traces, user impact                                                                         |
| **GitHub**                                  | Code                           | Deploys, code diffs, ownership                                                                            |
| **Atlassian** (Jira + Confluence)           | Work tracking + Knowledge      | Jira issues, Confluence pages, project context                                                            |
| **Notion**                                  | Knowledge                      | Docs, runbooks, databases                                                                                 |
| **Linear**                                  | Work tracking                  | Issues, projects, roadmaps                                                                                |
| **LaunchDarkly**                            | Feature flags                  | Flags, targeting, audit logs                                                                              |
| **Braintrust**                              | Observability                  | AI observability, logs, evals                                                                             |
| **[Cloudflare](/ai/connectors/cloudflare)** | Infrastructure + Observability | DNS, Workers, Zero Trust, audit logs, Radar, CASB, Logpush, and more — fourteen Cloudflare surfaces total |

The authorization flow requires you to be signed in to the vendor's platform with an account that has permission to grant third-party access. If the Connect button doesn't open the vendor's authorization screen, see Troubleshooting below.

### Setup-Required Providers

These providers need a short configuration form before Rootly AI can query them. Each has its own dedicated setup guide:

<CardGroup cols={2}>
  <Card title="AWS" icon="server" href="/ai/connectors/aws">
    Read-only cloud infrastructure via an IAM Role. CloudFormation, Terraform, or manual setup — plus optional EKS support.
  </Card>

  <Card title="Datadog" icon="dog" href="/ai/connectors/datadog">
    Logs, metrics, traces, dashboards, monitors, and incidents.
  </Card>

  <Card title="Grafana Cloud" icon="chart-line" href="/ai/connectors/grafana-cloud">
    Metrics, logs, dashboards, and alerts from your Grafana Cloud stack.
  </Card>

  <Card title="Grafana Managed" icon="chart-line" href="/ai/connectors/grafana-managed">
    The same signals from a self-managed Grafana instance.
  </Card>

  <Card title="New Relic" icon="chart-column" href="/ai/connectors/new-relic">
    Entities, NRQL, alerts, and golden metrics. US or EU region.
  </Card>

  <Card title="Semaphore" icon="code" href="/ai/connectors/semaphore">
    Pipelines, job logs, and CI/CD workflow context.
  </Card>

  <Card title="Custom (Any OAuth MCP)" icon="puzzle-piece" href="/ai/connectors/custom">
    Bring your own OAuth-based MCP endpoint. Add an allowlist of tools Rootly AI can call.
  </Card>
</CardGroup>

***

## The Provider Card

Every connector renders as a card with a status badge and a primary action.

<ParamField path="Status: Available">
  The provider can be connected. Click **Connect** to start the setup flow.
</ParamField>

<ParamField path="Status: Connected">
  Rootly AI can query this provider. The card shows **Configure** and **Disconnect** buttons — use Configure to update credentials or scoping, Disconnect to revoke the connection.
</ParamField>

<ParamField path="Status: Coming Soon">
  Rootly is working on this provider but it isn't connectable yet. The Connect button is disabled.
</ParamField>

<ParamField path="Status: Restricted">
  Your Rootly account doesn't have permission to manage this source. Ask an admin to enable the connection, or ask them to grant you the required permissions.
</ParamField>

***

## Data Handling

Rootly AI queries connectors **at investigation time only** — not on a schedule. When an investigation runs, Rootly AI calls the connector, reads the response, uses it in reasoning, and moves on. Rootly does not maintain a persistent copy of the connector's underlying data (your Datadog logs, Notion docs, GitHub diffs).

Query results *do* appear in the LLM traces Rootly logs to its evaluation and observability platform — as with every other tool call Rootly AI makes — so a connector response can be retained in trace form for quality monitoring. See **[Data Privacy for Rootly AI](/ai/data-privacy-for-rootly-ai)** for the retention boundary and what's included.

Credentials for setup-required connectors (API keys, IAM Role ARNs, service-account tokens) are stored encrypted and used only to query that connector on your behalf.

***

## Best Practices

* **Start with the observability and code connectors.** These are the two categories that consistently show up in "what caused this?" investigations. Sentry + GitHub covers most product-tier incidents; adding Datadog or Grafana on top covers infrastructure. Everything else layers value on top.
* **Connect the work-tracking connector your team actually uses.** Atlassian (Jira) or Linear — pick one. Connecting both when you only use Linear adds a source that never fires and clutters the picker.
* **Don't over-scope AWS.** Rootly AI works fine with narrowly scoped IAM permissions. Start with the AWS services you actually operate and expand later if Rootly AI's output is missing signal.
* **Grafana Cloud and Grafana Managed are mutually exclusive in practice.** Connect Grafana Cloud if your team is on the managed offering. Connect Grafana Managed if you self-host.
* **Reconnect after major credential rotations.** If you rotate the API key or IAM Role that Rootly AI uses, the connector status shows Connected but queries fail. Reconnect from the Configure button to re-authenticate.
* **Restrict who can manage connectors.** Connectors pull real customer data into investigation context. Limit the "manage connectors" permission to users who understand what each connector exposes.

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="The Connect button doesn't open the vendor's authorization screen" icon="triangle-exclamation">
    A browser popup blocker is the most common cause. Confirm you're not blocking popups from `rootly.com`, then try again. If the screen still doesn't appear, check whether your account on the vendor's platform has permission to authorize third-party apps — some organizations restrict this to admins only.
  </Accordion>

  <Accordion title="A connector shows Connected but Rootly AI says it can't reach the data" icon="plug-circle-xmark">
    Credentials rotated on the vendor side without the connector being reconnected. Open the connector's Configure screen and re-authenticate. Any specific failure reason will be surfaced when you save.
  </Accordion>

  <Accordion title="A provider I need isn't in the picker" icon="magnifying-glass">
    The catalog is the current supported set. If a provider is marked Coming Soon, it's on the roadmap. For anything else, use the **Custom** connector — it lets you point Rootly AI at any OAuth-based MCP endpoint. If neither option works, request the provider through support.
  </Accordion>

  <Accordion title="The card shows Restricted and I can't click Connect" icon="lock">
    Your Rootly account role doesn't include permission to manage connectors. Ask an admin to grant you the permission, or to run the setup on your behalf.
  </Accordion>

  <Accordion title="Rootly AI's investigation output doesn't cite a connector I connected" icon="circle-xmark">
    Rootly AI only reaches for connectors that carry relevant signal for the current investigation. If it isn't citing your connected Notion, that usually means the question didn't warrant a Notion lookup — not that the connector is broken. Confirm the connector is Connected, then try a prompt that explicitly targets its data (e.g., *"What does our runbook say about this?"* for Notion).
  </Accordion>
</AccordionGroup>

***

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="What's the difference between Connectors, Alert Sources, and regular Integrations?" icon="shapes">
    All three are ways Rootly connects to third-party tools, but they serve different purposes.

    **Alert Sources** bring events *into* Rootly (a Datadog monitor firing creates a Rootly alert).

    **Regular Integrations** let Rootly *push* actions into third-party tools (creating a Jira ticket when an incident is declared, posting to Slack when severity changes).

    **Connectors** let Rootly AI *read from* third-party tools while investigating.

    A single vendor can be all three simultaneously — the configurations are independent.
  </Accordion>

  <Accordion title="Do I need to configure a vendor as a Connector if I already have it set up as an Alert Source or regular Integration?" icon="link">
    Yes. Alert Sources and regular Integrations don't grant Rootly AI access to that vendor's data. If you want Rootly AI to read Datadog logs during investigations, connect Datadog as a Connector too — separate from any Datadog Alert Source you already have.
  </Accordion>

  <Accordion title="Does Rootly store the data it queries from connectors?" icon="floppy-disk">
    No. Rootly AI reads from connectors only during an investigation, uses the response, and doesn't keep a copy of the underlying data. See [Data Privacy for Rootly AI](/ai/data-privacy-for-rootly-ai) for full detail.
  </Accordion>

  <Accordion title="What if my tool isn't in the catalog?" icon="puzzle-piece">
    Use the **[Custom](/ai/connectors/custom)** connector. It lets you point Rootly AI at any OAuth-based MCP endpoint and specify an allowlist of tools it can call. Good for internal MCP servers or third-party tools not yet in the built-in catalog.
  </Accordion>

  <Accordion title="Can I disconnect a connector without deleting anything else?" icon="trash">
    Yes. Disconnecting removes the credentials Rootly uses to query the vendor and marks the card Available again. Historical investigations that referenced that connector keep their context — Rootly AI just won't be able to query the source anymore for future investigations.
  </Accordion>
</AccordionGroup>

***

## Related Pages

<CardGroup cols={3}>
  <Card title="Rootly AI Overview" icon="sparkles" href="/ai/ai">
    Parent page for the whole Rootly AI suite.
  </Card>

  <Card title="Data Privacy for Rootly AI" icon="shield" href="/ai/data-privacy-for-rootly-ai">
    What Rootly AI sees, retention, and model training controls.
  </Card>

  <Card title="Alert Sources" icon="bell" href="/alerts/alerts">
    The other integration surface — monitoring tools that ingest events into Rootly as alerts.
  </Card>
</CardGroup>