Ha ha. That's assuming the dev team wants to monitor apps. I've met many, many devs who have 0 desire to be woken up at night for crap they coded during the day. They just want to code.
It's incredibly common.
Not that I blame them, if you can work just 9-5, why wouldn't you?
I've never seen anything like that, nor have my dev and DevOps buddies, ever seen anything like what you just suggested.
Dismantle infra eng and make devs do everything? I support that, for one reason: a year from now I can charge consulting dollars when I come to fix these unstable, poorly documented, environments with minimal automation and HA.
Well I did that in the startup I worked in previously. And no, they are not gonna call you for your shitty service. They are pretty stable.
Guess what? We knew how to configure private clouds, loadbalancers, sharding and high availability. We pretty much know everything about Kubernetes/Amazon ECS et. al and related technologies and we didn't have any problems with monitoring or low level networking among others either.
Anyone can learn this shit. There is nothing special about it.
Don't hold your breath for seeing your consulting dollars, LOL. :D
By the description of it, the root cause of the problem is your setup. Dismantle the infra eng team and make the dev team to monitor their own apps.
By reading of your explanation devs should have more access and responsibilities.
You set up a half baked process and you are blaming the devs for it? Not cool.