Integrations

You can quickly connect your existing stack to Traversal. Once connected, Traversal begins analyzing metrics, events, logs, traces, deployments, system knowledge, Slack context, and more.

By integrating your observability stack, Traversal can analyze live incidents with full context and deliver meaningful insights when it matters most.

Access model — read-only by design

• We only require read-only API access to your systems and repositories.

• No agents to deploy. No write privileges to your data stores or code.

• Slack: we request the minimal messaging scope 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.

---

Step 1: Log into Traversal

After logging onto Traversal, go to Settings → Integrations.

The Onboarding Guide on the Integrations page can help you navigate the integration process.

Step 2: Connect Integrations

Context is critical when an incident is live. Traversal needs real-time access to your metrics, logs, and traces to understand what’s happening as it happens—not after the fact. The more data sources you connect, the more accurately Traversal can reason.

For best results, start with telemetry—it’s the most important integration. If you’re on Datadog, connect that first. If you’re on LGTM, starting with Grafana alone is great as long as your other data is routed there.

Once telemetry is in place, add GitHub and productivity tools.

Traversal supports a wide range of integrations, including:

Developer tools (Code changes, infrastructure changes, and LLM providers)

• Anthropic

• GitHub

• MotherDuck

• OpenAI

Productivity tools (Communication, documentation, and incident management)

• Confluence

• FireHydrant

• Jira

• PagerDuty

• Linear

• Notion

• ServiceNow

• Slack

Telemetry data (Alerts, dashboards, logs, metrics, and traces)

• Grafana

• VictoriaMetrics

• Mimir

• Sumo Logic

• ClickHouse

• New Relic

• Datadog

• Elasticsearch

• Loki

• OpenSearch

• Prometheus

• Splunk

• AppDynamics

• ThousandEyes

If any sources are missing, reach out to us and we'll guide you through our custom integration workflow.

Each integration requires a few configuration steps to ensure smooth functionality. Click on the name of each integration to get a step-by-step breakdown of how to properly connect that platform.

For example, configuring Anthropic follows the below steps:

Prerequisites

• An Anthropic account

• API access enabled

Part I

1. Go to console.anthropic.com

2. Navigate to API Keys

3. Click Create Key

4. Copy the generated API key

Part II

1. Enter the API key in the form above

2. Optionally specify a custom base URL for proxy configurations

For more information, see the Anthropic API documentation.

Step 3. Traversal starts Traversing your Stack

Completed integrations will show up in green.

After integrating your existing stack, you can immediately start exploring what’s going on in your system by asking natural language questions on Traversal’s Home page.

Some example questions you can start with:

1. What are the most recent PRs?

2. What are the impacts of my deployment on [XXX] endpoint?