12
Utilizing Continuous Integration (CI) Pipelines with Prometheus
As the trend toward Infrastructure-as-Code (IaC) continues, more and more focus is placed on ensuring that artifacts such as configuration files are version-controlled (usually via Git) and continuously synchronized. With the multiple files typically involved in a Prometheus stack – from Prometheus’s configuration file to rules files to Alertmanager’s configuration and everything in between – it can become difficult to ensure that every change to these files is properly vetted and safe to deploy.
Certainly, we can rely on code reviews, approvals, and branch protection rules on repositories to try to catch as many problems as we can. However, inevitably, things get missed, and ...
Get Mastering Prometheus now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
