[okdood64]

> When the oncall gets paged, an SLO should be in jeopardy in a way that requires immediate measures

> No SLO in jeopardy, or no immediate measure that needs to be taken?

A little contradictory here. Maybe your "or" should've been an "and". But anyways:

I can think of several scenarios for which an SLO is not in jeopardy for which you should get paged. All of which boils down to "Yes it is important for the business, our users, our brand" but still not worth having an SLO around because it's either 1) hard to measure or 2) too difficult to implement.

In an ideal world with infinite engineering resources on your team, you could have and _maintain_ an SLO for every part of the business that your system effects. In the real world, trade-offs need to made and certain key SLOs prioritized.

[raldi]

The first one is "p and q"; the negation of that is "(not p) or (not q)".

Could you describe one of the scenarios you're envisioning?