Skip to main content

SLOs Drive Operational Efficiencies, Visibility and Improved Business Benefits

As SLOs (service level objectives) grow in popularity their usage is becoming more mature. For example, 82% of respondents intend to increase their use of SLOs, and 96% have mapped SLOs directly to their business operations or already have a plan to, according to The State of Service Level Objectives 2023 from Nobl9, based on a survey of more than 300 IT professionals and executives conducted with Dimensional Research.


In addition, 95% of respondents say SLOs help them make better business decisions with 27% of companies stating that SLOs have saved them $500,000 or more.

SLOs are becoming an essential way to increase operational efficiency and improve business processes

"It was incredibly impressive to see the year over year growth in the market and the consistency of responses from our survey last year," said Marcin Kurc, co-founder and CEO, Nobl9. "The responses align with what we are seeing in the market. Enterprises across all industries are increasing their focus on system reliability to ensure customer experience, and doing this by finding new ways to leverage their new and legacy monitoring and observability tools. SLOs are becoming an essential way to increase operational efficiency and improve business processes."

Companies use observability tools to provide visibility and enable key functions such as security, operational efficiency, capacity planning, customer support, and increase development velocity. With fragmented tools — 72% use more than six observability tools — companies need to gain visibility not by consolidation that would hurt productivity, but by creating consistent definitions of reliability and expectations for various services.

"The survey responses are indicative of the broader trends we are seeing in the market around companies focusing on operational efficiency and business agility," said Stephen Elliott, Group VP, I&O, Cloud Operations and DevOps, IDC. "The pandemic drove more companies to the cloud, and with that, we have identified observability and monitoring to be key areas of focus. SLOs are one way for companies to manage their resources and get the most out of them."

Other key findings include:

■ 80% have an increased focus on system reliability due to the pandemic driving cloud adoption, remote workers and supply chain issues.

■ 94% are pursuing system reliability engineering, with most tasks being assigned to IT operations.

■ The ways companies are using monitoring and observability tools is increasing. More than 13 initiatives rely on monitoring and reliability with the most common being security, operations performance (uptime, performance, efficiency) and capacity planning.

■ Respondents identified 10 areas that require monitoring beyond networks, applications and databases, but most lack visibility, and the number is expected to grow.

■ 72% of companies use six or more monitoring and observability tools.

■ 76% prevented business interruptions using SLOs — but 9% have not implemented thresholds yet.

Methodology: All respondents had observability and monitoring responsibilities, and were IT professionals and executives at medium to large enterprise companies representing all seniority levels. Participants represented dozens of countries from five continents providing a global market perspective.

Hot Topics

The Latest

IT organizations have historically measured success by how quickly they can respond when something goes wrong. The entire discipline of Incident Management has been optimized around mean time to resolution, first-response SLAs and ticket closure rates. But new research suggests that even though this is a well-executed playbook, it's no longer enough to retain customers ...

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 ...

SLOs Drive Operational Efficiencies, Visibility and Improved Business Benefits

As SLOs (service level objectives) grow in popularity their usage is becoming more mature. For example, 82% of respondents intend to increase their use of SLOs, and 96% have mapped SLOs directly to their business operations or already have a plan to, according to The State of Service Level Objectives 2023 from Nobl9, based on a survey of more than 300 IT professionals and executives conducted with Dimensional Research.


In addition, 95% of respondents say SLOs help them make better business decisions with 27% of companies stating that SLOs have saved them $500,000 or more.

SLOs are becoming an essential way to increase operational efficiency and improve business processes

"It was incredibly impressive to see the year over year growth in the market and the consistency of responses from our survey last year," said Marcin Kurc, co-founder and CEO, Nobl9. "The responses align with what we are seeing in the market. Enterprises across all industries are increasing their focus on system reliability to ensure customer experience, and doing this by finding new ways to leverage their new and legacy monitoring and observability tools. SLOs are becoming an essential way to increase operational efficiency and improve business processes."

Companies use observability tools to provide visibility and enable key functions such as security, operational efficiency, capacity planning, customer support, and increase development velocity. With fragmented tools — 72% use more than six observability tools — companies need to gain visibility not by consolidation that would hurt productivity, but by creating consistent definitions of reliability and expectations for various services.

"The survey responses are indicative of the broader trends we are seeing in the market around companies focusing on operational efficiency and business agility," said Stephen Elliott, Group VP, I&O, Cloud Operations and DevOps, IDC. "The pandemic drove more companies to the cloud, and with that, we have identified observability and monitoring to be key areas of focus. SLOs are one way for companies to manage their resources and get the most out of them."

Other key findings include:

■ 80% have an increased focus on system reliability due to the pandemic driving cloud adoption, remote workers and supply chain issues.

■ 94% are pursuing system reliability engineering, with most tasks being assigned to IT operations.

■ The ways companies are using monitoring and observability tools is increasing. More than 13 initiatives rely on monitoring and reliability with the most common being security, operations performance (uptime, performance, efficiency) and capacity planning.

■ Respondents identified 10 areas that require monitoring beyond networks, applications and databases, but most lack visibility, and the number is expected to grow.

■ 72% of companies use six or more monitoring and observability tools.

■ 76% prevented business interruptions using SLOs — but 9% have not implemented thresholds yet.

Methodology: All respondents had observability and monitoring responsibilities, and were IT professionals and executives at medium to large enterprise companies representing all seniority levels. Participants represented dozens of countries from five continents providing a global market perspective.

Hot Topics

The Latest

IT organizations have historically measured success by how quickly they can respond when something goes wrong. The entire discipline of Incident Management has been optimized around mean time to resolution, first-response SLAs and ticket closure rates. But new research suggests that even though this is a well-executed playbook, it's no longer enough to retain customers ...

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 ...