This reminds me of something @chimeracoder was just asking about.
How does one resolve the emerging consensus for alerting exclusively on user-visible outages, with the undeniable need to learn about and react to things +before* users notice? Like a high cache eviction rate?
I love this post on the evolving state of the art of being on call. It's neat to get the perspective of someone "oncall-adjacent", not neck deep and sleep deprived.There's been a lot of chatter lately about how Service Ownership means engineers should be on-call. 🐝@djpiebob🐝 talks about how on-call has changed since the days when she was woken by the pager, and how #observability can be your new 💖valentine💖: honeycomb.io/blog/notes-fro…- This reminds me of something @chimeracoder was just asking about. How does one resolve the emerging consensus for alerting exclusively on user-visible outages, with the undeniable need to learn about and react to things +before* users notice? Like a high cache eviction rate?
