View on sreweekly.com A message from our sponsor, FireHydrant: Looking to cozy up with a good read this week? Check out “Your guide to better status pages.” It’s a mini masterclass on how to better communicate on your status pages. https://firehydrant.com/blog/your-guide-to-better-incident-status-pages/ Rule of 10x per 9 For every 9 you add to SLO, you’re making… Continue reading SRE Weekly Issue #404
Category: SRE
Posts related to Site Reliability Engineering
SRE Weekly Issue #403
View on sreweekly.com A message from our sponsor, FireHydrant: Signals is now available in beta. Sign up to experience alerting for modern DevOps teams: Page teams, not services. Ingest inputs from any source. Bucket pricing based on usage. And one platform — ring to retro — finally. https://firehydrant.com/blog/signals-beta-live/ Service Level Indicators A great overview of… Continue reading SRE Weekly Issue #403
SRE Weekly Issue #402
View on sreweekly.com A message from our sponsor, FireHydrant: Signals is now available in beta. Sign up to experience the difference: Page teams, not services. Ingest inputs from any source. Bucket pricing based on usage. And one platform — ring to retro — finally. https://firehydrant.com/blog/signals-beta-live/ Introducing Service Level Calculator Wow, this interactive tool for choosing… Continue reading SRE Weekly Issue #402
SRE Weekly Issue #401
View on sreweekly.com A message from our sponsor, FireHydrant: Join FireHydrant Dec.14 for a conversation about on-call culture and its effect on engineering organizations, featuring special guests from Outreach and Udemy. Gain a better understanding of what makes excellent on-call culture and how to implement practices to improve yours. https://app.livestorm.co/firehydrant/better-incidents-winter-bonfire-inside-on-call?type=detailed A Few Words About Blameless… Continue reading SRE Weekly Issue #401
SRE Weekly Issue #400
View on sreweekly.com A message from our sponsor, FireHydrant: How is FireHydrant building its alerting tool, Signals, to be robust, lightning-fast, and configurable to how YOU work? In this edition, of their Captain’s Log, they dive into CEL and how they’re using it to handle routing and logic. https://firehydrant.com/blog/captains-log-how-were-leveraging-cel/ A guide to Managing the First… Continue reading SRE Weekly Issue #400
SRE Weekly Issue #399
View on sreweekly.com A message from our sponsor, FireHydrant: Severity levels help responders and stakeholders understand the incident impact and set expectations for the level of response. This can mean jumping into action faster. But first, you have to ensure severity is actually being set. Here’s one way. https://firehydrant.com/blog/incident-severity-why-you-need-it-and-how-to-ensure-its-set/ Paper: How in the World Did… Continue reading SRE Weekly Issue #399
SRE Weekly Issue #398
View on sreweekly.com A message from our sponsor, FireHydrant: “Change is the essential process of all existence.” – Spock It’s time for alerting to evolve. Get a first look at how incident management platform FireHydrant is architecting Signals, its native alerting tool, for resilience in the Signals Captain’s Log. https://firehydrant.com/blog/captains-log-a-first-look-at-our-architecture-for-signals/ Precise Communication Saves Lives A… Continue reading SRE Weekly Issue #398
I’ll be at KubeCon North America
Hi folks, sorry for invading your inbox / RSS feed an extra time this week! I forgot to mention with yesterday’s issue that I’ll be at KubeCon this week. Hit me up for some SRE Weekly swag (patches, decals, and stickers). SRE WEEKLY
SRE Weekly Issue #397
View on sreweekly.com A message from our sponsor, FireHydrant: Incident management platform FireHydrant is combining alerting and incident response in one ring-to-retro tool. Sign up for the early access waitlist and be the first to experience the power of alerting + incident response in one platform at last. https://firehydrant.com/signals/ Modern rollback strategies The length and… Continue reading SRE Weekly Issue #397
SRE Weekly Issue #396
View on sreweekly.com A message from our sponsor, FireHydrant: DevOps keeps evolving but alerting tools are stuck in the past. Any modern alerting tool should be built on these four principles: cost-efficiency, service catalog empowerment, easier scheduling and substitutions, and clear distinctions between incidents and alerts. https://firehydrant.com/blog/the-new-principles-of-incident-alerting-its-time-to-evolve/ Translating Failures into Service-Level Objectives Using 3 high-profile… Continue reading SRE Weekly Issue #396