Summary
In this chapter, we’ve explored how to ensure that our Prometheus configuration, Prometheus rules, and Alertmanager configuration are properly validated using CI pipelines with GitHub Actions. This is a critical step toward the maturity of your Prometheus environment and enabling other teams who may not be Prometheus Subject Matter Experts (SMEs) to contribute to the monitoring environment without fear.
CI environments vary widely across the industry as there are a plethora of different CI tools available for use. But whether you use GitHub Actions, Jenkins, CircleCI, GitLab, or anything else, I hope this chapter has given you ideas on how to better integrate validation steps for your Prometheus environment into your CI tool of choice.
In our next chapter, we’ll continue exploring ways to build out mature monitoring environments by looking at how we can define and implement Service Level Objectives (SLOs) using Prometheus.
