Time-to-first-accepted-answer as a real SLO
Support volume looks healthy until you chart hours from question to is_solved. Last month p50 was 6 hours and p90 was 3 days — almost all of that p90 was weekend campus tickets.
We added an SLA banner on Question templates only. Discussions stay untimed on purpose.
What number would you publish without setting the community up to fail?

We hit the same wall on
time-to-first-accepted-answer. Replica lag was the surprise, not CPU.