Enable SLO-as-Code with Nobl9 and GitLab
May 9, 2022Quan To
Summary
This post introduces an integration with Nobl9 to enable SLO-as-Code. It details how to configure GitLab CI/CD variables (CLIENT_ID, CLIENT_SECRET, ACCESS_TOKEN, PROJECT, SLOCTL_YML) and a CI/CD job using the `nobl9/nobl9-ci-template` to automatically push SLO definitions to Nobl9 whenever the referenced SLOCTL_YML file changes. This allows for version-controlled SLO definitions and ensures consistency between the code repository and Nobl9.
More from the Log Management and Observability trail
- Green DevOps: Why carbon measurement belongs in your CI/CD pipeline
- Automate detection testing with GitLab CI/CD and Duo
- How to build CI/CD observability at scale
- Track vulnerability remediation with the updated GitLab Security Dashboard
- More granular product usage insights for GitLab Self-Managed and Dedicated