Going to AWS re:Invent 2026? Join us at booth 1871 for demos, giveaways, and more.
Meet with us

Why Your AI SRE Should be More than an Incident Bot

December 16 | 1 p.m. GMT

OR

December 16 | 10 a.m. PST

Martin Thwaites
Martin ThwaitesPrincipal Developer Advocate
Hannah Henderson
Hannah HendersonSenior Engineering Manager, AI
Ronald Ekambi
Ronald EkambiSenior Software Engineer II

We don’t hire SREs to fix incidents. We hire them as proactive teammates to help us hit specific goals, like safer releases, healthier systems, and more reliable software overall. Then we give them room to grow, and they get better the longer they work with us.

So why do most “AI SRE” tools stop at responding to alerts? What if your AI SRE could work the way a great SRE does: taking on goals, doing the proactive work between incidents, and learning how your team and systems operate over time?

Join the Honeycomb team for a look at what that could mean for your reliability practice, what an AI SRE can take on, and where humans should stay in the loop. Q&A included so submit your hardest AI SRE questions when you register or bring them live.

You’ll learn how to:

  • Define reliability goals that an AI SRE can work toward proactively, not just during incidents.
  • Evaluate AI by the strength of its evidence, starting with the quality of the underlying telemetry.
  • Match autonomy to risk so you can decide how much freedom AI gets for each service, and how that can grow as trust is earned.