SREday London 2026 Q1

Adriana Villela

Observability is a Team Sport! at Dynatrace

Amila Mahaarachchi

Building Abstractions That Matter: A Developer Platform on Kubernetes at WSO2

Andy Kuszyk

MCP is the new REST: making MCP our new API at Typeform

Birol Yildiz

The next evolution of incident response isn’t faster alerts at it’s autonomous resolution. Join ilert CEO Birol Yildiz as he shows how AI SRE agents now diagnose and remediate outages without waking anyone up. Learn how these systems combine observability data, deployment context, and code intelligence to restore services in minutes and hand over clean incident reports instead of 3 a.m. pages.

Birol Yildiz

Keynote: When Incidents Fix Themselves: AI SRE in action at ilert

Charles Weir

Major software disasters may be almost inevitable at but organisations and ecosystems can survive them. Learn how cyber continuity techniques can prepare your systems to limit damage and support recovery.

Christian Melendez

Two Autoscalers Walk into a Cluster: KEDA & Karpenter on Day-2 Duty at AWS

Dewan Ahmed

Keynote: Secure by Default: Building Confidence in AI-Driven Delivery at Harness

Dmitrii Iniutin

Beyond Terraform: Building Production Infrastructure with General-Purpose Languages at Seamflow

Ehsan Khodadadi

Your API monitoring was green. Dashboards calm. Then a quiet spike: cost per task up 40% at grounded answer rate down 8%, and users start regenerating responses twice as often. Infra metrics say “all good” , but the model silently shifted behavior after a prompt tweak plus a vendor embedding update. Non-AI-adopted SRE doesn’t page you here. ​AISRE would.

Goran Minov

This is an intermediate talk suitable for backend developers and cloud architects. It includes a code walkthrough of the Cloud Run Functions and a data analysis segment comparing the solution's effectiveness.

Heather Thacker

Your app works great on your laptop, in the dev environment. Then production hits 10x expected traffic during a marketing campaign and everything falls apart. Or maybe not, instead six months of data accumulates, causing the response times to be painfully slow. Load testing, stress testing, soak testing, and spike testing, they all sound similar, but address completely different problems, and most teams only do one, if at all.