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

# Integrations

> Connect your existing observability stack so Traversal can analyze live incidents with full context.

Once connected, Traversal begins analyzing metrics, events, logs, traces, deployments, system knowledge, Slack context, and more. The more data sources you connect, the more accurately Traversal can reason about what's happening in production.

## Access model — read-only by design

<Info>
  Traversal only requires read-only API access to your systems and repositories. There are no agents to deploy and no write privileges to your data stores or code.

  For Slack, Traversal requests the minimal messaging scope needed to post investigation results back into channels. This is limited to messages from the Traversal app and does not grant data-plane writes to your systems.
</Info>

***

## Connect your stack

<Steps>
  <Step title="Log into Traversal">
    After logging in, go to **Company Knowledge > Integrations**. Use the Onboarding Guide on the Integrations page to navigate the setup process.
  </Step>

  <Step title="Connect integrations">
    Traversal needs real-time access to your metrics, logs, and traces to understand what's happening as it happens — not after the fact.

    <Tip>
      Start with telemetry — it's the most important category. If you're on Datadog, connect that first. Once telemetry is in place, add GitHub and productivity tools.
    </Tip>

    Traversal supports the following integrations:

    <AccordionGroup>
      <Accordion title="Telemetry — alerts, dashboards, logs, metrics, and traces">
        * [Alertmanager](/integrations/alertmanager)
        * [AppDynamics](/integrations/appdynamics)
        * [Coralogix](/integrations/coralogix)
        * [Datadog](/integrations/datadog)
        * [Elasticsearch](/integrations/elasticsearch)
        * [Grafana](/integrations/grafana)
        * [Loki](/integrations/loki)
        * [Mimir](/integrations/mimir)
        * [OpenSearch](/integrations/opensearch)
        * [Prometheus](/integrations/prometheus)
        * [Sentry](/integrations/sentry)
        * [Splunk](/integrations/splunk)
        * [Tempo](/integrations/tempo)
        * [ThousandEyes](/integrations/thousandeyes)
        * [VictoriaMetrics](/integrations/victoria-metrics)
      </Accordion>

      <Accordion title="Developer tools — code changes and infrastructure changes">
        * [GitHub](/integrations/github)
        * [GitLab](/integrations/gitlab)
        * [MotherDuck](/integrations/motherduck)
      </Accordion>

      <Accordion title="LLM gateway — AI model providers">
        * [Anthropic](/integrations/anthropic)
        * [AWS Bedrock](/integrations/aws-bedrock)
        * [OpenAI](/integrations/openai)
      </Accordion>

      <Accordion title="Productivity — communication, documentation, and incident management">
        * [Confluence](/integrations/confluence)
        * [FireHydrant](/integrations/firehydrant)
        * [incident.io](/integrations/incident-io)
        * [Jira](/integrations/jira)
        * [Linear](/integrations/linear)
        * [Notion](/integrations/notion)
        * [ServiceNow](/integrations/servicenow)
        * [Slack](/integrations/slack)
      </Accordion>
    </AccordionGroup>

    Click any integration above for setup instructions, or select one in Traversal for a step-by-step walkthrough.

    <Note>
      If a source you need is missing, reach out and the Traversal team will guide you through the custom integration workflow.
    </Note>
  </Step>

  <Step title="Traversal starts analyzing your stack">
    Completed integrations appear highlighted in green.

    You can immediately start exploring your system by asking natural-language questions on Traversal's Home page. For example:

    * What are the most recent PRs?
    * What are the impacts of my deployment on the `[endpoint]` endpoint?
  </Step>
</Steps>