Resolve incidents faster, right from Slack
AI SRE to root cause incidents and triage alerts.
What is Traversal?
Traversal is an AI site reliability engineer that helps teams automatically resolve and prevent reliability issues. We scan logs, metrics, traces, recent deployments, and other signals to pinpoint likely root causes and suggest fixes—so incidents get triaged and resolved in minutes, not hours.
Traversal uses large language models (LLMs) to analyze telemetry and conversation context, generate explanations, and suggest next steps. Because LLMs can sometimes produce inaccurate or incomplete responses, please validate recommendations before acting.
With the Traversal Slack app, engineers can:
Start investigations
From any channel or DM - either by invoking Traversal manually, or through configuring custom auto-triggers
See investigations
See Traversal investigations for incidents or alerts shared directly in their Slack channels or DMs
Ask follow-up questions
Ask follow-up questions in natural language to refine the analysis
How Traversal works in Slack
- Start with @Traversal or /investigate in any channel/thread or DM
- Describe the incident (symptoms, affected service, runbook/alert link)
- Traversal replies in thread when results are ready
- Use /register-trigger to define criteria for auto-investigations
- Set scope and conditions (e.g., #alerts + severity: critical)
- Traversal automatically investigates matching messages
Slash commands
| Command | What it does |
|---|---|
| /investigate | Start a manual investigation. You'll be prompted to describe the incident (symptoms, affected service, links). Traversal replies in-thread when results are ready. |
| /register-trigger | Open a modal to create a Custom Trigger for automatic investigations. Define channel scope and AND/OR criteria (e.g., severity = critical). |
| /show-triggers | List all configured triggers across the workspace; from there you can remove ones you don't need. |
| /show-channel-triggers | List triggers scoped to the current channel; remove or adjust as needed. |
Quick Setup
Install the Traversal Slack app to your workspace
Contact our team to provision your workspace access and configuration
Invite @Traversal to your incident and alert channels
Set up automatic investigations for common alerts
Security & compliance
Slack data is used only to deliver the features described on this page. We do not use Slack data to train LLMs.
See privacy policy for retention and deletion practices.
All traffic encrypted in transit; tokens stored securely; Slack signature verification enforced.
We request only the minimum scopes needed for functionality.
AI disclaimer: Traversal uses generative AI and may produce inaccurate or incomplete outputs. Please validate recommendations before acting.
Privacy policy: https://www.traversal.com/legal/privacy-policy
Permissions we request (and why)
We follow the principle of least privilege and only request scopes needed for the features described here:
| Permission | Why we need it |
|---|---|
| commands | Enable the four slash commands above |
| chat:write | Post updates, summaries, and investigation results |
| app_mentions:read | Respond when someone mentions @Traversal |
| channels:read / groups:read / im:read / mpim:read | Read basic channel/DM metadata to anchor investigations |
| channels:history / groups:history / im:history / mpim:history | When added to a channel/DM, read recent history to build context (errors, timelines) and avoid asking humans to re-type details |
| files:read / files:write | Ingest helpful artifacts (logs, traces) and upload images in RCA reports |
| links:read / links:write | Detect links in messages and unfurl to companion UI when enabled |
| pins:read / pins:write | Pull context from pinned messages; pin significant milestones during incidents |
| reactions:read | Interpret emoji reactions on bot messages for feedback |
| users:read / users:read.email | Map Slack users to your Traversal account for a consistent experience |
| incoming-webhook | Post asynchronous alerts when no active WebSocket is available |
Support
Questions or issues? Contact us at support@traversal.com
Response target: within 2 business days