The State of Observability & Reliability in the AI Era
A 2-minute survey for SREs, DevOps and platform engineers on incidents, alert noise and AI.
- Short sections
- 7
- To complete
- ~2 min
Q1
How many separate tools/dashboards do you personally switch between during a typical incident?
What Does the Observability Survey Ask?
Short questions for SREs and DevOps teams on the parts of incident response that cost the most time, money and sleep.
Tool Sprawl
How many tools and dashboards you switch between during an incident, where the time goes, and what your MTTR looks like.
Alert Noise and On-Call Load
Hours lost to false alarms each week, how often you are on call, and what is driving burnout on your team.
Missed-Incident Risk
How much of the alert stream you receive turns out to be real, actionable issues.
Cost-Cutting Fallout
Whether pressure to cut observability spend has reduced your logging, tracing or retention, and what that did to debugging.
AI Adoption
Where AI actually shows up in observability and incident response today, from triage and investigation to agentic tooling.
Satisfaction and Renewal
How you rate your current observability setup and which factors, from cost to open standards, drive that score.
How Is the Survey Run?
How responses are collected, who they come from and how the results are reported.
- Fielding period
- September to December 2026
- Who responds
- SREs, DevOps and platform engineers, software engineers on call, security engineers and the people who lead those teams
- Format
- 15 questions across 7 sections, about 2 minutes. A work email is required and no name is asked for
- Reporting
- Results are published in aggregate only, broken down by role and company size. Individual responses are never published
Observability Survey FAQ
What the survey asks, who it is for and what happens to your answers.
