Maybe, one of these days, my SRE team can define SLOs that actually make sense. This "alert on whatever the customer wants" stance really really sucks.
If you're lucky, you work somewhere where nobody ever checks if any problems came from not having caught an incident. In that case, the top-right half of the diagram just disappears and developers get the privilege of... you know... sleep.
Some of the stories I have from the last place I worked, though.
When they first announced that devs would be on-call (including at 3:00am) for when the automated systems decided there was an issue, I panicked and pushed for creating a program that could do first-tier on-call support (based on rules that the devs owned, of course.)
And there were so many dumb situations where some downstream system borked and I ended up on a call all night literally unable to do anything. I figured this system could 1) weed out false positives, 2) identify when the problem was legitimate but not something my team could do anything about, 3) let us tell it to suppress certain types of alerts just for the night (if it was an issue worth looking into, but not one that needed dealt with before business hours), and 4) even take remediative action in some cases.
Folks told me all that was great. By the time it was done and ready to actually use, they'd changed their minds and decided none of what I'd specifically asked them to ok at the outset complied with their secret, unwritten "policy".
I ended up quitting that place over their absolutely cruel on-call policies. (And other things, but the on-call was the worst bit.)