We’re excited to introduce native Service Level Objective (SLO) management in Splunk Observability Cloud beginning with the release of SLOs to track the success rate of APM services. With this new built-in experience, we’re making it easier than ever for you to track the reliability and performance of your services that impact your critical user journeys and business goals.
Success Rate SLOs for APM Services
Observability SLOs are based on a Service Level Indicator (SLI), which is a metric that is important to meet for your service or infrastructure. SLIs can be defined on custom metrics and they are delivered out of the box for the success rate of APM services. By choosing a compliance period and a threshold, you can define a target that should be achieved for your service. Simple alerting will help you notify the right people when the error budget is being consumed too quickly or when you have missed your SLO target.
There are three ways to alert on SLOs in Observability Cloud:
- Breach Events - The SLO target has been missed for the compliance period. Best as a final indicator that reliability or performance should be prioritized.
- Budget Events - There may not be enough error budget remaining in this compliance period. Best for simple understanding of the alerting condition.
- Burn Events - The recent burn rate indicates a serious incident that could impact your SLO target. Best for proactive teams that want to leverage intelligent alerting.
In addition to SLO alerting, the new experience features an intuitive UX highlighting recent status to help you find the right SLO target and view the time windows where the SLO status was impacted.
Accessing SLOs
SLO management is included as part of the subscription for all Splunk Observability Cloud customers, for both suite and a la carte, so you can access today. There are no additional costs for this feature.
Explore our documentation to learn more, and start using SLOs in Splunk Observability Cloud today.
