YSYathartha Shekharinfluidifyai.hashnode.dev·3d ago · 8 min readRunbooks the On-Call Engineer Will Actually Open at 3amCross-posted from the Fluidify blog. Key takeaways Most runbooks are written by someone calm, at a desk, with full context, for a reader who is none of those things during an actual incident. That mi00
YSYathartha Shekharinfluidifyai.hashnode.dev·6d ago · 7 min readWho Owns the Pager When the Team Is Spread Across Time ZonesCross-posted from the Fluidify blog. Key takeaways Follow-the-sun on-call fixes the fatigue problem of one timezone carrying every 3 a.m. page, and creates a different one: ownership that spreads acr00
YSYathartha Shekharinfluidifyai.hashnode.dev·Oct 5 · 10 min read10 Best Self-Hosted On-Call Scheduling ToolsCross-posted from the Fluidify blog. If you need on-call scheduling that runs on your own infrastructure, the options look different from the usual PagerDuty or Opsgenie comparison. Those tools are Sa00
YSYathartha Shekharinfluidifyai.hashnode.dev·Oct 1 · 5 min readThe Cost Structure of Per-Seat Incident ToolingCross-posted from the Fluidify blog. Key takeaways Per-seat pricing in on-call and incident tools tracks headcount, not infrastructure cost or usage. The marginal cost of one more responder on a sche00
YSYathartha Shekharinfluidifyai.hashnode.dev·Sep 22 · 10 min read10 Best Open-Source On-Call Management ToolsCross-posted from the Fluidify blog. What "open-source oncall tool" actually covers Before the list: these ten tools solve different slices of the same broader problem, and conflating them is how team00
