Skip to main content

The State of Service Level Objectives 2022

Quan To
Nobl9

Businesses need happy customers in order to survive, and infrastructure teams need to meet reliability goals efficiently. Large cloud-native companies pioneered the service level objective (SLO) method to create a scalable relationship between operational staff and software services while maintaining customer loyalty and cost controls.

A recent survey of more than 300 IT managers and executives conducted by Dimensional Research and sponsored by Nobl9 titled The State of Service Level Objectives highlights how enterprises are currently using SLOs with their current monitoring and observability tools, and how many are looking to expand their use to achieve even further reliability goals and efficiencies.


The evidence is clear. It's not a question of if enterprises will adopt SLOs, but rather how they will do it. As SLOs grow in popularity, more than 8 out of 10 companies are planning to increase their use. In fact, SLOs are being used to provide visibility into their use of new technologies.

For example, 87% stated using SLOs for microservices would increase their performance. While many would expect SLOs to be used purely for IT operations, the research also shows that increasingly business teams (executives, manufacturing, product teams, R&D, marketing, finance, etc.) are using SLOs.

Most companies have a wide array of observability and monitoring tools

They commonly provide visibility into IT operations, but that data now also provides information directly into the business needs for security, compliance, AI/ML, and other uses. However, even with the large number of monitoring and observability solutions deployed, less than half of the companies surveyed have visibility into all their IT environments, and hybrid-cloud use is compounding the issue. Given the swift adoption of containers and microservices, it was staggering to see just 45% and 35% have visibility into those systems respectively.

SLO adoption has grown

More than 8 out of 10 companies are increasing SLO use. Typically, SLOs are created around user journeys, but now there is an emerging trend of creating SLOs to provide visibility into and to measure new technologies. This trend is supported by the overwhelming 94% that intend to map SLOs directly to business operations, and a significant 91% that indicate SLOs are improving decision making.

SLOs aligned to business operations prevent business impact and disruptions

In fact, more than 6 out of 10 companies indicated that SLOs aligned to business operations have already prevented business impact and disruptions. Given the tremendous value of SLOs, it is of little surprise that 71% of companies not using SLOs today plan to adopt them. In a world where technology quite literally enables and facilitates most businesses, visibility is key, to know what is going on, optimize business operations and decision making, and provide early warning indicators to stave off potential business losses.

One of the biggest sectors in a business that's indicating how SLOs will shape their future is in the security industry. Security is supported by 71% of a company's observability and monitoring tools as reported from the rising pressures to put security as a focal point for the overall well-being of a business, external influences in cybersecurity attacks and reducing liabilities in performance and efficiency are possibilities that cannot be ignored. Over 71% of businesses are monitoring observability tools that support and integrate SLOs for this purpose to counteract these types of plausible scenarios.

Future of SLOs

The 71% of businesses that aren't using SLOs today but plan on adopting them in the future for optimizing business operations are already missing out on minimizing potential business losses through early warning indicators. The outcomes that companies can gain from the use of SLOs may not seem to have much of an impact in the short term, but the importance that SLOs bring to businesses across many industries is increasing.

Quan To is Sr. Director Product Management at Nobl9

The Latest

Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...

Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

The State of Service Level Objectives 2022

Quan To
Nobl9

Businesses need happy customers in order to survive, and infrastructure teams need to meet reliability goals efficiently. Large cloud-native companies pioneered the service level objective (SLO) method to create a scalable relationship between operational staff and software services while maintaining customer loyalty and cost controls.

A recent survey of more than 300 IT managers and executives conducted by Dimensional Research and sponsored by Nobl9 titled The State of Service Level Objectives highlights how enterprises are currently using SLOs with their current monitoring and observability tools, and how many are looking to expand their use to achieve even further reliability goals and efficiencies.


The evidence is clear. It's not a question of if enterprises will adopt SLOs, but rather how they will do it. As SLOs grow in popularity, more than 8 out of 10 companies are planning to increase their use. In fact, SLOs are being used to provide visibility into their use of new technologies.

For example, 87% stated using SLOs for microservices would increase their performance. While many would expect SLOs to be used purely for IT operations, the research also shows that increasingly business teams (executives, manufacturing, product teams, R&D, marketing, finance, etc.) are using SLOs.

Most companies have a wide array of observability and monitoring tools

They commonly provide visibility into IT operations, but that data now also provides information directly into the business needs for security, compliance, AI/ML, and other uses. However, even with the large number of monitoring and observability solutions deployed, less than half of the companies surveyed have visibility into all their IT environments, and hybrid-cloud use is compounding the issue. Given the swift adoption of containers and microservices, it was staggering to see just 45% and 35% have visibility into those systems respectively.

SLO adoption has grown

More than 8 out of 10 companies are increasing SLO use. Typically, SLOs are created around user journeys, but now there is an emerging trend of creating SLOs to provide visibility into and to measure new technologies. This trend is supported by the overwhelming 94% that intend to map SLOs directly to business operations, and a significant 91% that indicate SLOs are improving decision making.

SLOs aligned to business operations prevent business impact and disruptions

In fact, more than 6 out of 10 companies indicated that SLOs aligned to business operations have already prevented business impact and disruptions. Given the tremendous value of SLOs, it is of little surprise that 71% of companies not using SLOs today plan to adopt them. In a world where technology quite literally enables and facilitates most businesses, visibility is key, to know what is going on, optimize business operations and decision making, and provide early warning indicators to stave off potential business losses.

One of the biggest sectors in a business that's indicating how SLOs will shape their future is in the security industry. Security is supported by 71% of a company's observability and monitoring tools as reported from the rising pressures to put security as a focal point for the overall well-being of a business, external influences in cybersecurity attacks and reducing liabilities in performance and efficiency are possibilities that cannot be ignored. Over 71% of businesses are monitoring observability tools that support and integrate SLOs for this purpose to counteract these types of plausible scenarios.

Future of SLOs

The 71% of businesses that aren't using SLOs today but plan on adopting them in the future for optimizing business operations are already missing out on minimizing potential business losses through early warning indicators. The outcomes that companies can gain from the use of SLOs may not seem to have much of an impact in the short term, but the importance that SLOs bring to businesses across many industries is increasing.

Quan To is Sr. Director Product Management at Nobl9

The Latest

Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...

Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...