InvestigationsWeb appUX/UI
Stop a running investigation
Cut off an investigation that is heading in the wrong direction instead of waiting for it to finish. Use the stop control in the composer while a run is active. The investigation keeps the stopped chain and how long it ran, and you can send a new follow-up in the same thread.InvestigationsWeb appSlackMicrosoft Teams
Keep investigations on the time window you asked for
Traversal no longer moves the incident time when you paste text into the new investigation composer or leave the message box. It still picks up context items from your message, and you can set the incident time explicitly.Follow-ups that ask for relative periods such as “today” or “the last 24 hours” now use the time you asked the follow-up, not the original investigation time. This keeps new and long-running investigation threads focused on current data.WorkersWeb appSlackMicrosoft TeamsUX/UI
Read Worker updates as structured summaries
Worker messages from Microsoft Teams now keep their headings, paragraphs, and lists in the web app instead of collapsing into one block of large text. Bulleted and numbered lines from Slack bot and alert messages also render as lists, so summaries, timelines, and next steps are easier to scan across both platforms.AnalyticsWeb app
Export cleaner analytics data to CSV
Session exports from Analytics now download as standards-based CSV files that open directly in spreadsheet tools. Exports leave out internal turn fields, label each investigation with its user-facing origin, and distinguish Microsoft Teams sessions from Slack sessions.Web appUX/UI
Compare chart values at a glance
Charts across Traversal now use a cleaner visual style with lighter labels, clearer gridlines, a dotted hover guide, and redesigned hover cards that align each series’ value. Hovering no longer dims the other bars, making it easier to compare Worker impact, investigation evidence, cost trends, and other chart data.IntegrationsGitHubGitLab
Connect GitHub Enterprise Server with an app
Organization admins can now connect a GitHub Enterprise Server app from Settings → Integrations. GitHub and GitLab connections can also be marked as read or write, so their configured access is clear when you review an integration.Usage limitsWeb appWorkers
Usage limits
You can now set usage limits for investigations across your organization, members, and Traversal Workers.Usage limits are managed by organization admins.From Settings → Usage:- Set separate limits for human-triggered, auto-triggered, and Worker-triggered investigations
- Set a per-member limit that caps each member separately
- Set daily and cycle limits for incident, alert, and custom Workers
- Give a specific Worker its own limit
- Create email alerts at percentage or credit thresholds
- See usage against every configured limit
IntegrationsMCPReliability
Faster, more resilient MCP connections
Traversal now opens only the MCP server that owns the tool it needs. Servers that are not used no longer add startup time, and a slow or misconfigured server cannot block the others.Timed-out connections retry once. If a server still does not respond, Traversal pauses it only for that investigation run while other investigations keep trying. Client-credentials tokens are created on first use and refreshed automatically after an authorization failure.Web appInvestigationsWorkersKnowledge BankUX/UI
A more capable ⌘K
⌘K now reaches more of Traversal. Alongside investigations, it finds your Workers and Knowledge Bank files, and you can deploy a new Worker straight from the menu. Workers show their live status in the results, so you can tell which one you want before you open it.
InvestigationsWeb appUX/UI
Smoother long investigations
Opening an investigation now puts its steps and reply in their final positions, so the page does not jump as the steps load. In a long investigation, the side rail stays inside the chat and keeps the message you are reading centered.Follow-ups no longer reload the session once for every completed turn. They stay responsive, and the investigation steps remain visible after the new reply appears.IntegrationsGitHubGitLabInvestigations
Better GitHub Actions investigations and clearer fixes
Traversal can now follow GitHub’s authenticated redirects to read workflow logs and artifact ZIPs during an investigation, including large files served from GitHub’s result-storage hosts.When Traversal opens a pull request or GitLab merge request, the description starts with a link to the source investigation and explains what prompted the change and who requested it, when known. Reviewers can move from a failing workflow to the proposed fix without reconstructing the context.WorkersSlackMicrosoft Teams
New Worker commands in Slack and Microsoft Teams
Start and stop a Worker without leaving the channel it works in.- Slack —
/traversal worker startopens the start form, and/traversal worker stopstops the channel’s Worker. See Slack. - Microsoft Teams —
@Traversal worker-startopens the start form, and@Traversal worker-stopstops the Worker, in channels, group chats, and meeting chats. See Microsoft Teams.
IntegrationsAzure
Azure integrations
Traversal now connects to Azure.Azure Resource Manager and Azure Monitor — resource inventory and configuration, change history, Resource and Service Health, access and identity metadata, and Azure Monitor logs and metrics, all through one connection. Authentication uses Microsoft Entra Workload Identity Federation — Traversal creates no credential of its own, and you grant it Reader and Log Analytics Reader on exactly the subscriptions you choose.Azure DevOps — correlate incidents with recent code changes: repositories, pull requests, diffs, and review threads, alongside your telemetry evidence. Supports both Azure DevOps Services and on-premises Azure DevOps Server. A single read-only personal access token is all that’s needed to connect.InvestigationsKnowledge BankWeb app
Use Skills in any investigation
Attach a Skill when you start an investigation or send a follow-up, and Traversal follows that procedure for the turn. Type/ to pick one, start typing its name and
press Tab, or choose + → Add skills. The Skill stays on your message, so
anyone reading the investigation can see which procedure guided it.
InvestigationsWeb appSlackMicrosoft Teams
Attach any file to an investigation
You can now attach any file type to an investigation — logs, JSON, HAR captures, Excel workbooks — instead of having unsupported files greyed out or dropped. Traversal reads Excel sheets as tables and summarizes HAR captures request by request, leading with failures. HAR summaries leave out headers, cookies, and request bodies, which can carry credentials. The 25 MB per-file limit still applies.Microsoft TeamsWorkers
Traversal in private channels, shared channels, and meetings
Add@Traversal to private and shared Microsoft Teams channels to investigate
or deploy a Worker there, once your Teams admin updates to the latest
Traversal app package.Workers can also join meetings on their own. Set a rule that matches meeting
names, and when a matching meeting is created, Traversal joins its chat and
starts a Worker. Automatic joins need a Microsoft 365 admin to grant three
additional Graph permissions. See Microsoft Teams.IntegrationsDatadog
Search Datadog Flex Logs
Traversal now searches Datadog Flex Logs alongside your indexed logs. Flex often keeps months of history and the high-volume streams that indexed retention drops, so investigations can find evidence from well before your indexed window. If your organization uses Flex, Traversal finds it automatically, with no extra setup.Knowledge BankWeb app
Add PDFs to your Knowledge Bank
Upload PDFs — architecture docs, runbook exports, process diagrams — to the Knowledge Bank, and Traversal reads them during investigations, including the diagrams and screenshots inside. Previously, Traversal could store a PDF but not read it.WorkersWeb app
Turn any investigation into a team debugging session
An investigation used to belong to the person who started it. Now click Collaborate with Worker to hand it to a Worker: it picks up what the investigation found, and your whole team can work the problem with it in one place — asking questions, chasing leads, and building on each other’s findings. If a Worker is already on the investigation, the button takes you to it, so everyone ends up in the same session.
WorkersSlackMicrosoft Teams
Ask a Worker what it has found so far
When a Worker starts an investigation, it now receives findings as they are produced instead of waiting for the final report. Ask for an update while the investigation is still running, and the Worker can summarize the latest evidence, explain what it is still checking, and use those findings in the rest of the channel conversation.APIMCPWeb app
Service accounts for API and MCP workflows
Give your scripts, pipelines, and shared MCP clients an identity owned by your organization. Investigations belong to the service account, and replacement keys on the same account can continue its existing sessions.Organization admins can create accounts under Settings → Account management → Service accounts, issue and rotate API keys, disable access, and review session activity from the last seven days. Requests use the account’s current role; accounts created in the web app start with Member access.Service-account keys support the Sessions API and Traversal MCP. Service accounts are rolling out by deployment. See the Service accounts guide for setup, permissions, and key management.IntegrationsDatadog
Investigate real-user impact with Datadog RUM
Traversal can now query Datadog Real User Monitoring during an investigation to measure customer impact and connect frontend symptoms with backend evidence. It can count affected sessions or users, isolate regressions by route, release, browser, device, or geography, and inspect representative errors, resources, actions, views, and long tasks.RUM findings link to the matching query and time range in Datadog RUM Explorer. When Datadog provides request, trace, or span IDs, Traversal can use them to continue the investigation in APM and logs. Traversal filters RUM evidence before sending it to the agent and does not retrieve Session Replay recordings.Datadog RUM is rolling out to enabled organizations. It requires an existing Datadog connection with access to the relevant RUM applications. See the Datadog setup guide for setup, examples, and coverage limitations.IntegrationsKubernetes
Investigate Kubernetes clusters
Traversal can now inspect Kubernetes clusters during an investigation using scoped, read-onlykubectl commands. It can examine workloads, events, logs,
resource usage, rollout history, and cluster topology, then correlate what it
finds with evidence from your other integrations.Connect any Kubernetes-conformant cluster through a Traversal Connector using
ServiceAccount credentials, or use the streamlined AWS EKS setup with
short-lived, cross-account authentication. Your Kubernetes RBAC remains the
authoritative boundary for what Traversal can read.See the Kubernetes setup guide to connect a cluster.IntegrationsGitHub
Investigate GitHub repositories in depth
Traversal can now combine GitHub API data with a temporary checkout of an allowed repository during an investigation. It can search and analyze the wider codebase, inspect remote references, and use read-only GitHub CLI operations for pull requests, issues, workflows, releases, and other repository context.Repository checkouts run in an ephemeral agent sandbox. Traversal limits access to the repositories allowed by your GitHub integration and rejects customer repository writes. Public GitHub and GitHub Enterprise are supported, including private instances reachable through a Traversal Connector.See the GitHub setup guide for setup and access details.Integrations
PagerDuty integration
Traversal now connects to PagerDuty to pull incident details, on-call coverage, and escalation history into an investigation — who’s on call right now, what’s currently firing, and how an incident has escalated so far. A single read-only API key is all that’s needed to connect.See the setup guide to connect your account.WorkersWeb appUX/UI
Pinned Workers in the sidebar
Pin a Worker from the Workers page and it shows up in the left sidebar with a live status beacon, badged with the platform it works in. The beacon updates as the Worker’s state changes, so one that picks something up while you’re deep in an investigation tells you at a glance. Hover a row to read what it’s working on right now, or to Unpin it.
See the Workers console.ConnectorProcessorSecurityAPI
Set up the Traversal Connector and Processor yourself
You can now deploy and manage the Traversal Connector and Traversal Processor right from your Integrations page.You can set up the Traversal Connector yourself from the Integrations page in Traversal. Open the Connectors tab, create a Traversal Connector and give it a name, then sign its certificate in the UI. Traversal gives you the commands to deploy it in your environment, and shows its health and connection status once it’s running.Set up the Traversal Processor the same way. Open the Processors tab, create a Traversal Processor, sign the certificate, pick a size for your log volume, and watch its ingestion status as it runs.Set up and manage both from your Integrations page.See Traversal Connector and Traversal Processor.Major releaseKnowledge BankWeb app
The new and improved Knowledge Bank is generally available
Everything Traversal knows about your systems in one place, plus the last mile only your team can add.
Knowledge Bank: the Traversal Wiki, Memories, Uploaded docs, and Skills.
- The Traversal Wiki — a window into Traversal’s Production World Model: its own documentation of your environment, organized by service and written entirely from your connected systems. No input from your team produced any of it, and Traversal regenerates it as your systems change, reporting what each pass added, updated, and removed. Comment on a page and it carries the correction forward.
- Memories — the durable facts Traversal picks up working alongside you. It proposes what’s worth keeping and waits for a person to approve, in the web app or in the same Slack thread.
- Skills — your team’s own procedures, shaping the steps an investigation takes.
- Uploaded docs — the runbooks, business constraints, and workarounds your systems don’t record.
IntegrationsAWS
Investigate live AWS infrastructure
Traversal can now inspect your live AWS environment during an investigation using the AWS Account integration. The agent can describe resources, read configuration, and pull operational data across services such as EC2, EKS, RDS, Lambda, load balancers, and networking, then connect what it finds with evidence from your other integrations.Access is read-only and uses a cross-account IAM role with short-lived STS credentials instead of long-lived AWS access keys. Download the pre-filled CloudFormation template from Traversal and deploy it in each AWS account you want the agent to investigate.See the setup guide to connect your first account.WorkersWeb appUX/UI
Deploying a new Worker explains your options
Deploying a new Worker used to assume you already knew how the Worker types differed. Now each option describes itself as you pick it, so you’re not guessing which one to choose.Each card says what that Worker does and what you get from it — an Incident Worker investigates as soon as it joins and writes the postmortem at the end; an Alert Worker triages every alert and replies in its thread with a verdict, recognizing repeat alerts and reusing prior work; a Custom Worker has no preset behavior and follows the instructions you give it. So at the moment you deploy, you can tell whether the channel wants an incident responder, an alert triager, or something of your own design.
WorkersSlackUX/UI
Investigation links in Slack
When a worker points to an investigation, the link now renders as a mention chip — an icon plus the investigation’s own title — rather than a bare blue URL that looked like every other link in the channel.Those titles read better too. Investigations started by a worker or an MCP client are now named for their subject rather than for the request, so a channel of worker links says “Grafana query failures” where it used to say “Investigate Grafana query failures”. Titles already written are unchanged.See using Traversal in Slack.WorkersSlackMicrosoft TeamsWeb app
Edit custom instructions from chat
You could already tailor a Worker by editing its custom instructions on the Workers page. Now you can just tell it what you want in chat — from Slack, Microsoft Teams, or a web Worker — and it updates those instructions itself. Last-mile tailoring happens directly in the tools where you already work.Say what you want in plain language. For example, you can ask your Worker to:- Prioritize or ignore certain alerts — tell an Alert Worker which alerts matter and which ones to leave alone.
- Tag the responsible team — have an Incident Worker notify the right people as more information emerges.
- Check the deployment dashboard first — point a Worker at the evidence you’d reach for yourself.
WorkersSlack
Custom Workers
Workers are a powerful, flexible harness for Traversal’s Production World Model and Causal Search Engine. Incident Workers and Alert Workers package that intelligence into opinionated experiences for specific SRE use cases. Custom Workers open the same capabilities to the long tail of work your team wants Traversal to take on.Give a Custom Worker a mission in plain language, and it follows the channel and acts on that direction. Deploy one into:- A deployment channel — to watch a rollout as it goes out and flag the change that caused a regression.
- A support channel — to surface the recurring problem behind a run of customer reports.
- A team or project channel — to follow ongoing operational work and keep a running picture of where it stands.
Major releaseWorkersWeb appSlackMicrosoft Teams
The Traversal Workers release
Incident Workers in general availability, Alert Workers in public beta, and a new web experience for both.Scan your workspace, and Traversal proposes the Alert and Incident Workers to deploy plus the naming conventions to auto-deploy against.
SlackKnowledge Bank
Approve memories from Slack
When Traversal proposes a memory during a Slack investigation, you can now approve or reject it in the same thread. The card shows the memory name and the text being saved. The memory stays pending until a person decides — same as in the web app.See using Traversal in Slack.IntegrationsAWS
Amazon CloudWatch integration
Traversal now connects directly to Amazon CloudWatch to pull metrics and logs during investigations, using a cross-account IAM role. Deploy a CloudFormation template in the AWS account you want Traversal to read from, and it correlates CloudWatch signals with your other connected telemetry.See the setup guide to connect your first account.APIKnowledge Bank
Manage Knowledge Bank content through the API
The new Knowledge Files API lets you manage the knowledge your team contributes to Traversal programmatically. List, upload, download, replace, and delete runbooks, reference documents, and agent skills to keep Traversal in sync with your existing documentation workflows.The API covers team-authored documentation and skills. It does not expose Traversal’s Auto-created knowledge or agent memories.Major releaseWeb appKnowledge Bank
The new Knowledge Bank
Knowledge Bank is now one place to see everything Traversal knows about your systems — what it worked out on its own, and what your team has taught it.- Auto-created — Traversal’s own documentation of your environment, written from your connected integrations: code, metrics, logs, traces, alerts, tickets, and existing docs. It takes no input from your team to produce, and Traversal keeps regenerating it as your systems change — so anyone can read up on an unfamiliar service instead of asking around. Where you know something the data doesn’t show, leave a comment and Traversal folds it in.
- Skills — reusable procedures that shape the steps Traversal takes, so an investigation follows the way your team actually works.
- Documentation — runbooks, context files, and the constraints and workarounds your systems don’t record, expanding what Traversal has to reason over.
- Memories — what Traversal has learned working alongside you. It proposes what’s worth keeping and waits for a person to approve, so it gets sharper the more you use it.
Major releaseMicrosoft Teams
Traversal comes to Microsoft Teams
Traversal is now available in Microsoft Teams. Mention @Traversal in a channel, group chat, or direct chat with an incident description, and it runs a root-cause investigation across your connected observability tools — posting the report back into the thread with citations and a link to the full session in the web app. Ask follow-up questions in the same thread to dig deeper.A Teams administrator installs the app once; see the installation guide to get set up, and using Traversal in Teams for what you can do with it.APIInvestigations
Stream session status over the API
The Sessions API now provides a Server-Sent Events endpoint atGET /v1/sessions/{session_id}/events. Connect
once to receive the current status and each status change, instead of polling
while Traversal investigates.The stream sends keepalive comments during long-running investigations and
closes when the session becomes idle, failed, or cancelled. You can then
retrieve the final conversation with GET /v1/sessions/{session_id}.ProcessorMajor release
Throughput improvements for the Traversal Processor
Traversal Processor 0.4.0 ships alongside the 0.4.0 Helm chart with a rebuilt ingest and processing engine, delivering massive improvements to throughput and reliability under heavy load.- Higher throughput — up to ~80,000 records/s (~300 MB/s) per pod on the
largesize tier. - One-knob sizing —
size: normal|largesets CPU, memory, and internal tuning to validated presets. See sizing and throughput. - Deeper observability — a new and more detailed set of
processor.*metrics.
APIInvestigations
Choose investigation depth over the Sessions API
The Sessions API now accepts an optionalthinking_mode on
both session creation and follow-ups. Pass deep to force a thorough
root-cause analysis, fast for a quick exploratory pass, or leave it as the
default auto to let Traversal pick — existing integrations need no changes.Follow-ups now also count toward the same per-organization concurrency limit
as new sessions, so a burst of follow-ups is throttled with a 429 the same
way session creation already is.Web appAnalytics
A clearer picture of Traversal adoption
We’ve fully revamped the Analytics page, now available to Org Admins at app.traversal.com/analytics. It gives you a clear picture of how Traversal is being adopted and used across your organization, all in one place.- Usage over time — sessions and active users, with period-over-period comparison so you can track adoption week over week.
- Who’s using Traversal — top users and top channels, a Top Investigators panel, and an activity heatmap showing engagement across your team.
- Session detail — breakdowns by origin (Web, Slack, API, MCP) so you can see where investigations are being started.
WorkersSlackInvestigations
Workers read live incident transcripts
When your team runs an incident on a live video call, a Worker can now read the call’s transcript in real time and fold it into its work. It picks up what’s said out loud but never typed into Slack — the fix someone just tried, the theory forming on the call, even how people are reacting to Traversal’s own suggestions — and uses those cues to adjust course and stay current with where the room actually is.Live calls generate a lot of chatter, so under the hood Traversal distills the transcript down to what matters — cleverly filtering the noise rather than handing the Worker the raw feed — so it stays sharp and focused without overloading its context.Live transcripts are in private beta. Talk to your Traversal contact to connect your team’s calls.Web appUX/UI
Jump to anything with ⌘K
One for the power users: press ⌘K anywhere in the web app to open a quick search. Start a new investigation, jump to any past one by typing its name, or open your integrations, all from the keyboard. Arrow keys move through the list and Enter opens, so you never have to reach for the mouse.
Web appUX/UI
24-hour time format
Prefer a 24-hour clock? A new Time format option in your personalization settings switches Traversal from 12-hour AM/PM to 24-hour. It flows through the entire app — evidence displays, investigation timelines, the times you type into an investigation, everywhere a timestamp appears — so times read the way you expect no matter where you are.
Security
Single-tenant SaaS deployment
A new deployment option that sits between multi-tenant SaaS and full BYOC: a dedicated, single-tenant Traversal instance running in an isolated, Traversal-operated AWS account — its own domain, no infrastructure shared with any other customer, SSO required, and data encrypted at rest (AES-256) and in transit (TLS 1.3). You get hard tenant isolation without having to run and maintain Traversal in your own cloud. See deployment options.Web appUX/UI
Navigate long sessions
When you’re deep in an investigation, it’s natural to keep asking follow-ups — and a session can grow into a long back-and-forth. A new navigator makes those long sessions easy to move through by their question-and-answer pairs — jump straight back to any exchange instead of scrolling, and hover to preview what’s there.
Major releaseWorkersSlack
Traversal Workers
A new, more capable way to work with Traversal. Rather than waiting to be summoned, a Worker joins a channel and works alongside your team like a teammate — reading the situation, gathering context, and doing what’s worth doing on its own. During an incident, a Worker joins the moment the channel is created, investigates autonomously, follows the incident in real time, and drafts a post-mortem when it resolves.Web appUX/UI
Timezone preference
Set a personal timezone in your personalization settings so every timestamp across Traversal shows in your local time instead of UTC — no more mental math when reading an incident timeline.MCPIntegrations
Connect your own MCP servers
Connect any external MCP server as a data source — a great way to tailor Traversal to your stack with tools and systems we don’t support out of the box. Point it at an internal service or a third-party MCP server and its tools become available to the agent during investigations.Web appUX/UI
New navigation rail
A redesigned left navigation rail makes it faster to move between your sessions, integrations, and settings, with a cleaner layout that stays out of your way.
MCPInvestigations
SlackAlert IntelligenceUX/UI
Channel management
A new settings page to see every Slack channel Traversal is active in and manage them in one place — turn on Alert Intelligence for a channel and set its custom instructions, so every investigation in that channel follows the same guidance no matter who runs it.Web appUX/UI
Smoother follow-up quoting
Quoting part of a previous response in your follow-up is smoother — highlight the text you want to reference, hit Add to chat, and it’s attached to your next message with the composer focused and ready, so it’s clear exactly what you’re asking about.
InvestigationsWeb app
Generate files to download
Traversal can now generate files you can download and share — reports, PDFs, spreadsheets, and more. Ask for a deliverable and the agent produces it inline, ready to download straight from the session.
Web appSlackUX/UI
Slack session visualization
Sessions that originate in Slack now render with a custom Slack visualization in the web chat — showing who sent each message, which channel it came from, and whether any custom instructions were applied. Because Slack channels are multiplayer, knowing who said what matters — a shared incident channel has many voices, and the visualization keeps them straight. Alerts are rendered more cleanly too, so a Slack-triggered investigation reads clearly from the web app.
Investigations
Ask Traversal how it works
Traversal can now answer questions about its own documentation, so you can ask how a feature works right where you’re working. New users can even have Traversal onboard them — walking through what it does and how to get the most out of it.
InvestigationsSlackWeb app
Custom instructions
Give Traversal standing instructions so you don’t have to re-type your preferences every time — point it at specific runbooks, prescribe steps, or set output preferences like “be brief” or “suggest an owning team.” Two layers:- Personalization — your own instructions, applied to every investigation you run, in Slack and the web app.
- Channel custom instructions — instructions applied to every investigation in a Slack channel, no matter who runs it. Admins can also toggle Alert Intelligence mode per channel from the same console.
MCP
Web appUX/UI
Overhauled chain-of-thought
Traversal’s “chain-of-thought” loading state has been redesigned to be more legible and to better represent what the agent is actually doing as it investigates — including a clearer view of which integrations it’s using, and when.
Web appUX/UI
Redesigned login page
Your first touchpoint with Traversal got a full refresh — rebuilt on the new design system for a cleaner, more modern first impression, consistent with the rest of the product.
Web appUX/UI
A new design system
We’ve rolled out a new design system across every page of the product — a more open, modern feel with lighter borders and larger corner radii. We also refined the color palette and sharpened legibility throughout, including a polished dark mode. It’s especially noticeable on the home page and the session view, and in how we render code snippets.MCPInvestigations
Lightning mode
A fast investigation path built for the rapid back-and-forth of agent-to-agent work over MCP. A first pass typically returns in 30 seconds to two minutes — fast enough for a real conversation between your agent and Traversal rather than a single slow round trip. You can always follow up to go deeper.Alert IntelligenceSlack
Tune the definitions of noisy alerts
When Alert Intelligence flags an alert as noise, its response now includes a Tune Alert Definition button. Click it and Traversal drafts an updated alert definition — the specific change that stops the alert from firing on non-issues — ready for you to review and apply.
ConnectorSecurity
PrivateLink connectivity
Connect your environment to Traversal over AWS PrivateLink so traffic between your network and your Traversal deployment stays on the AWS backbone and never crosses the public internet. Paired with the outbound-only Connector, it gives you a fully private data path — no public endpoints, nothing exposed. See PrivateLink.ConnectorSecurity
Traversal Connector
A lightweight, outbound-only service you deploy in your environment that lets Traversal securely reach your private data sources — databases, internal APIs, and on-prem observability — without any inbound access. It opens a single encrypted, outbound tunnel, so there are no inbound firewall rules to manage and nothing in your network is exposed or listening for external traffic. It runs entirely in your environment, under your operational control. See the Traversal Connector.ProcessorSecurity
Redaction with the Processor
The Traversal Processor runs alongside the Connector in your environment and redacts sensitive data — PII, secrets, customer identifiers, or any fields you define — before it ever leaves your network. You own the rules (regex patterns and structured JSON keys), so Traversal only ever receives what you’ve explicitly allowed, and sensitive values never reach our control plane.InvestigationsUX/UI
Request analysis
When an investigation traces a request across services, Traversal now renders an inline request-analysis component right in its answer — a visual diagram of the request’s path across services, where it broke, and the errors behind each hop, alongside the key logs. Because it can pull from many log indices at once, you can see exactly where in a request an issue arose — the failing hop, the service, and the error in context.
APISecurity
Personal API keys
Create and manage your own API keys from settings to authenticate with the Traversal API and the MCP server.Alert IntelligenceSlack
Alert summary reports
Run/traversal alert-summary in any alert channel to generate an insights
report over a time period you choose — a digest of what fired, how often, and
what’s worth attention — so you can spot noisy monitors and recurring issues at
a glance.
Alert IntelligenceSlack
Alert Intelligence
Traversal now replies to every alert in the Slack channels it watches with an assessment — how urgent it is and why, and, for alerts that are just noise, how to tune them. You never have to tag anything.
API
Programmatic investigations (Sessions API)
Kick off investigations, ask follow-ups, and pull results entirely over HTTP with a self-service API key — the same capabilities you get in the app, now available to your own scripts, runbooks, and internal tools. See the API reference.IntegrationsWeb appUX/UI
Easier integration setup
Connecting a data source is more self-serve: every integration shows a live connection-health badge, credentials are verified the moment you connect (and rolled back if they fail), and you can test a query against a connected integration right from settings.
MCPAPI
Work with Traversal from your AI client (MCP)
The Traversal MCP server lets any compatible AI client — Claude Code, Cursor, Claude Desktop, and others — run investigations, ask follow-ups, and retrieve results. When called from another agent, Traversal acts as a peer your local agent works alongside, handing work back and forth until the incident is understood.Investigations
Post-mortems
Traversal produces a first-draft post-mortem so your team can skip the assembly work — reconstructing the timeline, writing up what happened, drafting follow-ups — and focus on the fixes. Generate one on demand by tagging Traversal. See post-mortems.Investigations