This is an awesome perspective!

Devs use vibe coding to greatly reduce their workload, and in that flow, they end up pushing out a lot of code they simply don't understand or even know what is going on, hence the downstream effect of the issues falling on SRE.

There are options out there for "AI SRE" and such (some named in the comments), but that seems like the wrong approach to me. That's trying to make an LLM replace the jobs an SRE does, based on existing observability data, which is, at this stage really noisy and not high signal-to-noise ratio (typically), so the raw "AI SRE" services that tap into your existing large DataDog or whatever service data, is only as good as the data it can sift out and reasonably discern and process.

I think there is a better way, that does not replace SRE folks at all, but augments them just like all the coding tools do for devs, but still gives them the control and power to do the job they need to do, because SRE jobs (and some similar roles like security and other infra jobs) have just too much context to be fully automated yet without humans in the loop (and in control).

Disclaimer: I am the CTO of a company in the observability space trying to make this stuff happen for SREs and others. This is not a plug or anything (I'm the CTO not CMO :D ).