Curated articles, resources, tips and trends from the DevOps World.
Summary: This is a summary of an article originally published by the source. Read the full original article here →
In the previous article SRE Onboarding, I discussed the concept of SRE and how SRE could help in the context of my current organisation. This article is a follow-up, a collection of tips I want to share after setting and fixing of our alerting system.
To make the alerting system great again, the first step is to have a mutual understanding of it in the team.
This further enable us to build Continuous Integration and Continuous Deployment (CICD) pipeline (Jenkins in our case) for the alerting system.
In this way, only the alarms we are interested in will be triggered, and since these alarms are listed in the configuration, we know exactly which alarms will be triggered.
Made with pure grit © 2024 Jetpack Labs Inc. All rights reserved. www.jetpacklabs.com