Four Key Pillars to a Leading Observability Practice

Mimi Shalash
Splunk
Learn more about Cisco Splunk

Splunk's latest research reveals that companies embracing observability aren't just keeping up, they're pulling ahead. Whether it's unlocking advantages across their digital infrastructure, achieving deeper understanding of their IT environments or uncovering faster insights, organizations are slashing through resolution times like never before.

The companies achieving the most powerful business outcomes are recognized as "observability leaders," excelling across the four critical stages of observability: foundational visibility, guided insights, proactive response, and unified workflows. Achieving "leader" status in observability unlocks more than just visibility because it empowers organizations with a deep, actionable understanding of their digital ecosystems. This translates directly into business returns, delivering a 2.6x annual ROI. In practical terms, that means smoother operations, fewer disruptions, and more time spent innovating rather than firefighting.

Let's explore the four key pillars that form the foundation of a world-class observability practice:

1. AI: A critical observability tool to help remediate issues

Automation is a cornerstone of an effective observability practice and elevates operational efficiency. As IT environments expand and grow increasingly complex, maintaining visibility over the full ecosystem of tools and technologies presents a growing challenge. Combine this with the volume of alerts that ITOps and engineering teams manage daily and the manual intervention becomes unsustainable. AI and machine learning (ML) solutions reduce the cognitive load off teams by dynamically recalibrating baseline metrics and detecting anomalies that static thresholds might overlook.

The latest data from Splunk highlights just how impactful AI and ML solutions can be with 85% of respondents reporting resolving at least half of their alerts. Additionally, 65% rely on AIOps for automated root cause analysis, giving teams the intelligence they need to stay ahead of issues.

Becoming an observability leader requires more than just basic monitoring. It requires advanced solutions that understand the normal patterns of your IT environment to then automatically detect anomalies. Consider a straightforward scenario: an unexpected CPU spike occurs on a cluster node, triggering an alert that requires quick, actionable insights. With an advanced observability tool, the system might recommend redistributing workloads across nodes to prevent service disruptions. Or it could initiate an automated remediation workflow via integrations with orchestration tools, ensuring rapid resolution without manual intervention.

2. Build a dedicated platform engineering team

Integrating AI and ML solutions is just one piece of what sets observability leaders apart. The competitive edge lies in how these technologies are embedded into platform engineering. Platform engineering isn't just about tools and processes, it's about empowering software engineers to do what they do best: create. By adopting standardized toolchains, workflows, and self-service platforms, teams minimize time spent managing tools because they've codified making the right thing to do, the easy thing to do.

The research shows that 73% of organizations are already embracing these practices and 58% of observability leaders recognize that this isn't just a trend. Rather, it's becoming the hallmark for continuous innovation, enabling seamless automation, scalability, and enhanced developer experience.

3. Harness control of the telemetry pipeline

At the heart of platform engineering, beyond automation and scalability, it's about maintaining control. Knowing exactly where your data flows, where it originates, and staying firmly in control of it isn't just important, it's essential. Ownership over data is the lifeline of every organization. Today, over 75% of observability leaders have adopted OpenTelemetry, solidifying it as the industry standard for collecting and controlling critical data. This open framework seamlessly integrates with other tools, bringing together data from multiple sources for complete visibility.

The result? A flexible observability practice that fosters innovation, reduces dependencies, and empowers businesses to grow on their own terms. With OpenTelemetry, you're not just building observability, you're building the freedom to evolve and innovate without limits.

Tapping into OpenTelemetry's full potential isn't just about adopting the technology. It also requires having the right talent in place and that comes with its own set of challenges. The report indicates that many companies are struggling with a shortage of people possessing the expertise on the open source project. To bridge the gap, organizations should prioritize training existing team members on how to configure, manage, and optimize OpenTelemetry pipelines and build this strategy into bullet #2.

4. Remember that observability is a team sport

Lastly, organizations must learn that true observability isn't achieved in isolation. Nearly three-quarters (73%) of observability leaders said they saw an improvement in their mean time to resolve (MTTR) after combining their observability and security workflows and tools. This highlights the importance of keeping observability tools connected across teams. When teams have cross-functional visibility into each other's workflows, they're better equipped to solve issues faster and prevent them from happening again.

While every team — observability and security — share the ultimate goal of business success, they may not share the same immediate objectives. Finding common tools and testing shared data sources can help iron out workflow differences, paving the way for future convergence.

Scaling with observability

As cloud reliance grows and AI tools multiply, IT environments will become even more complex, leaving organizations without full control over every tool interacting with their infrastructure. In other words, organizations must build a world-class observability framework to ensure that no part of their infrastructure operates without the necessary oversight. After all, every security professional knows … what you can't see can haunt you.

Observability practices don't just happen overnight. They require thoughtful planning, the right tools, and a continuous commitment to refining processes and integrating insights across teams. By focusing on enhancing the way people work, businesses can turn complexity into opportunity and maintain control in an ever-evolving digital landscape. Staying ahead of chaos is just good business sense — and the best way to firewall your future.

Mimi Shalash is Observability Advisor at Splunk, a Cisco company

Related Links

Hot Topics

Related Vendors

The Latest

MEAN TIME TO INSIGHT Podcast - Episode 24: Network Observability Tool Sprawl

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

Capacity Isn't a Guess: Observability-Driven Sizing for On-Prem Databases

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

5 Security Principles Every Entrepreneur Should Apply to Leadership

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Signs It May Be Time to Reassess Your IT Infrastructure Strategy

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Enterprise Edge AI Reaches Inflection Point

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

AI Is Hitting Operational Limits

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

Alert Fatigue Is No Longer a Morale Problem, It's a Reliability Risk and a System Failure

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

Most Enterprises Think They Can Switch AI Vendors in a Month ... Most Who've Tried Couldn't

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Your Observability Stack Has a Telemetry Pipeline Problem

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

Operator to Orchestrator: 80% of IT Pros See Shift in Role as AI Permeates Workflows

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

Four Key Pillars to a Leading Observability Practice

Mimi Shalash
Splunk
Learn more about Cisco Splunk

Splunk's latest research reveals that companies embracing observability aren't just keeping up, they're pulling ahead. Whether it's unlocking advantages across their digital infrastructure, achieving deeper understanding of their IT environments or uncovering faster insights, organizations are slashing through resolution times like never before.

The companies achieving the most powerful business outcomes are recognized as "observability leaders," excelling across the four critical stages of observability: foundational visibility, guided insights, proactive response, and unified workflows. Achieving "leader" status in observability unlocks more than just visibility because it empowers organizations with a deep, actionable understanding of their digital ecosystems. This translates directly into business returns, delivering a 2.6x annual ROI. In practical terms, that means smoother operations, fewer disruptions, and more time spent innovating rather than firefighting.

Let's explore the four key pillars that form the foundation of a world-class observability practice:

1. AI: A critical observability tool to help remediate issues

Automation is a cornerstone of an effective observability practice and elevates operational efficiency. As IT environments expand and grow increasingly complex, maintaining visibility over the full ecosystem of tools and technologies presents a growing challenge. Combine this with the volume of alerts that ITOps and engineering teams manage daily and the manual intervention becomes unsustainable. AI and machine learning (ML) solutions reduce the cognitive load off teams by dynamically recalibrating baseline metrics and detecting anomalies that static thresholds might overlook.

The latest data from Splunk highlights just how impactful AI and ML solutions can be with 85% of respondents reporting resolving at least half of their alerts. Additionally, 65% rely on AIOps for automated root cause analysis, giving teams the intelligence they need to stay ahead of issues.

Becoming an observability leader requires more than just basic monitoring. It requires advanced solutions that understand the normal patterns of your IT environment to then automatically detect anomalies. Consider a straightforward scenario: an unexpected CPU spike occurs on a cluster node, triggering an alert that requires quick, actionable insights. With an advanced observability tool, the system might recommend redistributing workloads across nodes to prevent service disruptions. Or it could initiate an automated remediation workflow via integrations with orchestration tools, ensuring rapid resolution without manual intervention.

2. Build a dedicated platform engineering team

Integrating AI and ML solutions is just one piece of what sets observability leaders apart. The competitive edge lies in how these technologies are embedded into platform engineering. Platform engineering isn't just about tools and processes, it's about empowering software engineers to do what they do best: create. By adopting standardized toolchains, workflows, and self-service platforms, teams minimize time spent managing tools because they've codified making the right thing to do, the easy thing to do.

The research shows that 73% of organizations are already embracing these practices and 58% of observability leaders recognize that this isn't just a trend. Rather, it's becoming the hallmark for continuous innovation, enabling seamless automation, scalability, and enhanced developer experience.

3. Harness control of the telemetry pipeline

At the heart of platform engineering, beyond automation and scalability, it's about maintaining control. Knowing exactly where your data flows, where it originates, and staying firmly in control of it isn't just important, it's essential. Ownership over data is the lifeline of every organization. Today, over 75% of observability leaders have adopted OpenTelemetry, solidifying it as the industry standard for collecting and controlling critical data. This open framework seamlessly integrates with other tools, bringing together data from multiple sources for complete visibility.

The result? A flexible observability practice that fosters innovation, reduces dependencies, and empowers businesses to grow on their own terms. With OpenTelemetry, you're not just building observability, you're building the freedom to evolve and innovate without limits.

Tapping into OpenTelemetry's full potential isn't just about adopting the technology. It also requires having the right talent in place and that comes with its own set of challenges. The report indicates that many companies are struggling with a shortage of people possessing the expertise on the open source project. To bridge the gap, organizations should prioritize training existing team members on how to configure, manage, and optimize OpenTelemetry pipelines and build this strategy into bullet #2.

4. Remember that observability is a team sport

Lastly, organizations must learn that true observability isn't achieved in isolation. Nearly three-quarters (73%) of observability leaders said they saw an improvement in their mean time to resolve (MTTR) after combining their observability and security workflows and tools. This highlights the importance of keeping observability tools connected across teams. When teams have cross-functional visibility into each other's workflows, they're better equipped to solve issues faster and prevent them from happening again.

While every team — observability and security — share the ultimate goal of business success, they may not share the same immediate objectives. Finding common tools and testing shared data sources can help iron out workflow differences, paving the way for future convergence.

Scaling with observability

As cloud reliance grows and AI tools multiply, IT environments will become even more complex, leaving organizations without full control over every tool interacting with their infrastructure. In other words, organizations must build a world-class observability framework to ensure that no part of their infrastructure operates without the necessary oversight. After all, every security professional knows … what you can't see can haunt you.

Observability practices don't just happen overnight. They require thoughtful planning, the right tools, and a continuous commitment to refining processes and integrating insights across teams. By focusing on enhancing the way people work, businesses can turn complexity into opportunity and maintain control in an ever-evolving digital landscape. Staying ahead of chaos is just good business sense — and the best way to firewall your future.

Mimi Shalash is Observability Advisor at Splunk, a Cisco company

Related Links

Hot Topics

Related Vendors

The Latest

MEAN TIME TO INSIGHT Podcast - Episode 24: Network Observability Tool Sprawl

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

Capacity Isn't a Guess: Observability-Driven Sizing for On-Prem Databases

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

5 Security Principles Every Entrepreneur Should Apply to Leadership

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Signs It May Be Time to Reassess Your IT Infrastructure Strategy

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Enterprise Edge AI Reaches Inflection Point

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

AI Is Hitting Operational Limits

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

Alert Fatigue Is No Longer a Morale Problem, It's a Reliability Risk and a System Failure

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

Most Enterprises Think They Can Switch AI Vendors in a Month ... Most Who've Tried Couldn't

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Your Observability Stack Has a Telemetry Pipeline Problem

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

Operator to Orchestrator: 80% of IT Pros See Shift in Role as AI Permeates Workflows

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...