Traversal

Meet Ali. Before joining Traversal, he worked on Pinecone’s vector database and billing infrastructure — building metering pipelines to process billions of metric events — and developed the server proxy for their multi-tenant product. Today he works on Traversal’s core infrastructure to ingest and organize metrics data in a novel way that makes it easier for AI Agents to pinpoint the right signals during incident investigations. When he and his fellow engineers aren’t discussing the best representation for high-cardinality metrics, they’re debating the merits of Xi'an Famous Foods versus Cafe Mogador. “Lunch at the Traversal office is never a dull affair. I love how everyone here has such strong opinions and curiosity about food, and how that carries over to meal time.” If you’re excited to join a team that cares as much about metrics as they do about hand-pulled noodles, Traversal is the spot for you. Find the full list of open roles at Traversal’s New York City office in the comments.

re:Invent may be over, but the momentum around AI SRE is only growing. Last week in Vegas, we spoke with thousands of engineers who visited our booth to learn how AI SREs can prevent incidents and remediate them quickly when they happen. Enthusiasm often came with a healthy dose of skepticism about whether AI SREs can deliver real value — especially if they require heavy integrations to get started. That made it particularly valuable to walk attendees through live demos of four Traversal features and to highlight the range of integration models we support. As our CEO Anish Agarwal shared last week, we’re making big bets on becoming a daily-use system for engineering teams in 2026 (link in comments) — and it was fun to see the excitement around those plans in person. Thanks to everyone who made the week in Vegas unforgettable, and see you next year! #AWSreInvent

Driving down downtime never looked so good. If you’re at re:Invent, stop by Booth #1391 to learn how you can get a free ride in one of our Traversal cars wherever you’re headed in Vegas. While you’re at it, grab some stylish swag (it’s going fast) — and learn how our AI SRE saves teams hours spent triaging alerts and troubleshooting incidents, so they can eliminate downtime and focus on building resilient systems. #AWSreInvent

Loving the energy at AWS re:Invent! Last night’s turnout at Traversal's booth (#1391) was incredible, and today is shaping up to be more of the same. We have 12 Traversal team members on hand to help people understand how our AI SRE not only helps engineers respond quickly to critical incidents, but also understand their systems before things go wrong. (And a few current customers stopping by to answer questions about their experience with Traversal). If you haven’t swung by yet, come say hello for live demos, in-depth conversations, and some sought-after swag and prizes (we even had a line for them last night). We’d love to see you. #AWSreInvent

Hey re:Invent 👋 Just like your most complicated incidents — we’ve got your ride around Vegas covered. (We all know how difficult it can be getting around the Strip) Stop by Booth #1391 next week to learn how you can get a free ride in one of our custom Traversal cars from 4-8 pm. While you’re there, pick up some awesome swag and prizes (keep your eyes here for more soon) and learn how our AI SRE can save your enterprise time and money by helping engineers proactively understand their systems and respond quickly when things go wrong. #awsreinvent #reinvent2025 #lasvegas

Traversal has been growing quickly these past few months. At re:Invent, we’re excited to share a few of the new features we’ve been building — along with examples of how Fortune 50 teams are using Traversal in production. A few of our customers will even be at our booth for a couple of hours each day to talk through their experience. If you’ll be at re:Invent and want to discuss what AI SRE could look like in your organization — or how to approach a pilot — I’d love to connect 1-on-1. You can DM me or book time using the following link: https://lnkd.in/djV5jG95.

Grateful for this incredible team today and every day. Happy Thanksgiving 🦃

Book 30 minutes with Anish at AWS re:Invent to dig into your AI SRE questions. Link in the comments.

KubeCon in a nutshell: great people, wild on-call stories, and a lot learned about how AI SREs can help. The Traversal team had an incredible time meeting everyone at KubeCon2025 last week — answering questions, demoing our core features, and listening to unbelievable engineering stories shared on our "on-call phone.” We commiserated. We laughed. And we talked about solutions. Here’s something we can all agree on: troubleshooting doesn't have to be this painful. Traversal helps teams prevent incidents with smart alert prioritization and system health exploration. And when issues do happen, we make remediation faster and less stressful — so engineers can get back to sleep or to parties, and so their spouses don’t get paged at 2am on their behalf (yes, that really happened to an engineer we spoke with). We can't wait to continue these conversations at AWS re:Invent in December! See you in Vegas? #KubeCon #reInvent2025 #SRE #DevOps

Most AI pilots die in the InfoSec and procurement stage. This is especially true of AI SRE products, which need access to sensitive company log data. We explain why, and how to avoid it. When vendors demand root access, intrusive agents, and broad cloud API permissions before proving they can deliver value, it typically stalls momentum and kills a pilot before it ever gets started. We even heard from a customer that another AI SRE vendor had asked to install a sidecar in every pod — just for the pilot! Here’s the thing: an AI SRE's job is primarily to interpret telemetry, not create it. Asking for invasive access early is often a signal that a vendor is either taking technical shortcuts or intentionally vying for vendor lock-in. There's a smarter path. At Traversal, some of our largest deployments run entirely on read-only API access to existing observability platforms like Datadog, ServiceNow, or Splunk. When accuracy demands more, we move to pipeline integration (Kafka, Cribl, OpenTelemetry) to deepen analysis without adding operational overhead. Agents and sidecars? They’re rarely necessary, if ever. The other place pilots get stuck: LLM approval. Many enterprises maintain pre-approved model lists, and vendors who can't adapt to your existing AI infrastructure force you into months of additional InfoSec reviews. The gold standard isn't a single integration pattern — it's flexibility. Start with the lightest integration (usually API access), prove value quickly, and expand only as needed. Work with vendors who adapt to your environment, not the other way around. Our latest blog breaks down the spectrum of access models, the trade-offs between API queries and pipeline integration, and why model flexibility matters for enterprise AI SRE deployments. Check the link in the comments to learn more.