corpus.blog
41554 blogs · 4,756,248 posts Claim your blog
Record · corpus.blog/posts/01a087b7-7e52-7324-838d-7fbc76501468

006: Building better on-call routines for engineering teams

oldschoolburke.com · published 18 January 2025

A record is what was published and who pointed at it. The text of the post is not held here: read it at the source, or at its Wayback capture.

Read the post at oldschoolburke.com Wayback capture
0blogs citing
First cited
—
Most recent
—
Rank this month
not ranked
Links from this post
12
Words captured
2,298

Cited by

No blog we hold has cited this post yet.

Links from this post

Link
Host
https://leaddev.com/call/why-call-pain-sociotechnical-problem?ref=oldschoolburke.com
leaddev.com
https://leaddev.com/personal-development/values-runbook-leadership?ref=oldschoolburke.com
leaddev.com
https://leaddev.com/reporting-metrics/how-run-great-incident-post-mortem?ref=oldschoolburke.com
leaddev.com
https://www.pagerly.io/blog/navigating-on-call-compensation-in-the-tech-industry-in-2023?ref=oldschoolburke.com
pagerly.io
https://docs.google.com/document/d/1beiyQ-tdVWZj0qcFbsFaaQk-rtjACa0tLkOv3WQYzWQ/edit?ref=oldschoolburke.com
docs.google.com
https://cloud.google.com/blog/products/management-tools/shrinking-the-time-to-mitigate-production-incidents?ref=oldschoolburke.com
cloud.google.com
https://blog.danslimmon.com/2017/10/02/what-makes-a-good-alert/?ref=oldschoolburke.com
blog.danslimmon.com
Three Questions to Help Triage Your Dashboards Read at the source ↗
adrianhoward.com
https://sre.google/sre-book/monitoring-distributed-systems/?ref=oldschoolburke.com
sre.google
https://leaddev.com/reporting-metrics/how-run-great-software-incident-post-mortem?ref=oldschoolburke.com
leaddev.com
https://sre.google/sre-book/service-level-objectives/?ref=oldschoolburke.com
sre.google
https://leaddev.com/culture/building-better-call-routines-engineering-teams?ref=oldschoolburke.com
leaddev.com