Slide 5
Slide 5 text
5
The project Our post-project findings
● Requirements
○ Enablement of observability
practices for developers
○ Abstract Monitoring-As-Code
complexity from developers
● Enabled developers to configure their
APM objects from a simple yaml file
○ Particularly SLIs/SLOs
● Defining SLOs as code early also helps
with automate testing and other
tooling outside of the observability tool
● But integration with each tool can be
complex
● SLIs are often the same across
projects, but leaving it to developers
completely creates discrepancies
● A lot of moving pieces: endpoints,
tooling, SLIs, SLOs, owners,
notifications etc.
A story about SLO as code
Customer project: observability adoption