Skip to main content

APM and Observability: Cutting Through the Confusion — Part 8

Pete Goldin
APMdigest

So after all this discussion, what do the experts say about whether you need APM, observability or both?

Start with: APM and Observability - Cutting Through the Confusion - Part 7

“In today's complex digital landscape, organizations need both APM and Observability to not only react to issues but to anticipate and mitigate them proactively, ensuring robust performance and resilience,” says Gab Menachem, VP ITOM at ServiceNow.

"Organizations will absolutely continue to leverage both approaches, particularly as the number of solutions in the market that support both approaches increases," Bryan Cole, Director of Customer Engineering at Tricentis, agrees.

"Most organizations use a combination of tools," adds Gurjeet Arora, CEO and Co-Founder of Observo AI. "It's rare to find a single solution that serves every team's needs. DevOps may rely on telemetry data pipelines, while application teams use APM tools, and security teams use SIEM platforms. Ideally, these tools integrate with each other and share a common data layer, but in reality, priorities differ by role. What matters most is having a strategy that allows each team to extract value from telemetry without duplicating data or increasing costs unnecessarily."

One Tool Fits All

Why choose APM or Observability when you can have both? Modern tools increasingly combine both observability and APM, bringing together deep insights for legacy applications and observability for distributed, cloud-native systems, says Varma Kunaparaju, SVP and GM for Cloud Platform and OpsRamp Software at HPE.

"It's becoming increasingly clear that for many, a combined approach, leveraging both APM and observability functionalities within a single, well-integrated tool, offers the most comprehensive solution for their monitoring and diagnostic requirements," confirms Arun Balachandran, Senior Product Marketing Manager, ManageEngine APM Solutions.

Ideally, organizations should aim for an integrated platform that combines both APM and observability, advises Menachem from ServiceNow. The objective isn't to accumulate more tools but to achieve deeper insights.

Andreas Grabner, Fellow DevRel and CNCF Ambassador, Dynatrace, agrees, "Ideally, organizations wouldn't need to manage separate tools. The most effective approach combines APM and observability into a single platform that provides unified data, context-rich insights, and automation. Fragmented tooling leads to data silos and slower issue resolution, while a converged platform improves visibility, collaboration, and time-to-value."

A unified platform serves as a single source of truth, streamlining resolution processes, enhancing accountability, and empowering informed decision-making across the board, Menachem from ServiceNow adds.

Integrated solutions can offer convenience, optimized operations and more robust performance for complex systems, Kunaparaju of HPE adds.

"Organizations increasingly recognize that they need unified platforms rather than point solutions," Rakesh Gupta, Head of Product Management at Observe points out. "The market is clearly moving toward consolidation, with 'single pane of glass' becoming a standard requirement from IT leadership."

There are tools that do both, but just as with any other tool purchase, you must weigh the pros and cons out there, warns Chrystal Taylor, Tech Evangelist at SolarWinds. There may be tools developed specifically for APM that have the benefit of greater maturity and feature sets that haven't been worked into observability tools out there. There may also be ways to integrate that data into your observability tools to get the best of both worlds. There are many options, so it's important to find the one best suited to your organization's needs and budget.

The trend is toward unified platforms that incorporate both capabilities, but organizations should evaluate their specific requirements before assuming one solution fits all, Paul Appleby, CEO of Virtana, concludes.

Observability with a Side of APM

Many of the experts recommend the tool combination in the form of a comprehensive Observability platform that includes APM among multiple other capabilities — and this concept further supports the view that APM is a subset of Observability, discussed in Part 3 of this series.

While some organizations choose to use both APM and Observability, it isn't a necessity, according to Emily Nakashima, VP of Engineering at Honeycomb. "Since APM is a subset of observability, organizations with a well-crafted observability strategy can utilize an observability tool to get everything APM offers and more."

"APM is just one part of the observability picture," explains Bahubali Shetti, Senior Director, Product Marketing, Elastic. "While APM focuses on identifying what's wrong within a specific service or set of services, observability helps you understand why by connecting signals across your entire environment using AI and machine learning. Full observability enables correlation of metrics, logs, and traces to uncover root causes, analyze patterns, and generate context-aware recommendations."

Shetti adds that with features like an AI Assistant, users can ask questions like, "Why is my checkout latency spiking?" and receive insights that automatically connect traces, logs, infrastructure metrics, and even internal knowledge like GitHub issues or support tickets. Observability also brings advanced capabilities like anomaly detection, pattern recognition, event categorization, and predictive analytics, allowing teams to move from reactive troubleshooting to proactive optimization. When combined with APM data, these capabilities deliver the end-to-end visibility and intelligence users need to resolve issues faster and scale systems more effectively.

"Both can co-exist, but for cost and complexity reasons, it is likely that organizations will move to the more encompassing observability approach," says Sven Delmas, VP of Research at Mezmo. "Note that an observability solution may or may not be just one tool."

Today organizations can expect to have APM in their observability tool but not necessarily vice versa, adds Hugo Kaczmarek, Director of Product, APM Suite at Datadog.

Keeping It Separate

Even though the experts recommend combining tools to get the best of both worlds, some organizations still rely on separate tools — whether due to legacy systems, departmental preferences, or unique functional requirements, says Balachandran from ManageEngine.

"And even the solutions that are a blend of both worlds — usually the result of acquired companies and merged toolsets — end up focusing on more of one than the other, with the lesser of the two simply there to provide context to the other or, worse, to be little more than box-checkers to pass an RFP," adds Leon Adato, Principal Technology Advocate, Catchpoint. "So companies probably will need both. More specifically, different teams within an organization will need the capabilities of one more than the other."

Unified Visibility and Actionable Insights

"What's most important is that organizations take a close look at what different tools and platforms offer and ensure that everything they require regarding APM/observability capabilities are met — whether that be through one tool, two tools, or five," says Cole from Tricentis.

Ultimately, the most important factor is ensuring that whichever tools are in place deliver unified visibility and actionable insights across the entire technology stack, from the application layer all the way down to the underlying infrastructure, recommends Balachandran from ManageEngine.

Start with: APM and Observability - Cutting Through the Confusion - Part 9, covering open source's impact on the evolution Observability.

Pete Goldin is Editor and Publisher of APMdigest

Hot Topics

The Latest

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

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

APM and Observability: Cutting Through the Confusion — Part 8

Pete Goldin
APMdigest

So after all this discussion, what do the experts say about whether you need APM, observability or both?

Start with: APM and Observability - Cutting Through the Confusion - Part 7

“In today's complex digital landscape, organizations need both APM and Observability to not only react to issues but to anticipate and mitigate them proactively, ensuring robust performance and resilience,” says Gab Menachem, VP ITOM at ServiceNow.

"Organizations will absolutely continue to leverage both approaches, particularly as the number of solutions in the market that support both approaches increases," Bryan Cole, Director of Customer Engineering at Tricentis, agrees.

"Most organizations use a combination of tools," adds Gurjeet Arora, CEO and Co-Founder of Observo AI. "It's rare to find a single solution that serves every team's needs. DevOps may rely on telemetry data pipelines, while application teams use APM tools, and security teams use SIEM platforms. Ideally, these tools integrate with each other and share a common data layer, but in reality, priorities differ by role. What matters most is having a strategy that allows each team to extract value from telemetry without duplicating data or increasing costs unnecessarily."

One Tool Fits All

Why choose APM or Observability when you can have both? Modern tools increasingly combine both observability and APM, bringing together deep insights for legacy applications and observability for distributed, cloud-native systems, says Varma Kunaparaju, SVP and GM for Cloud Platform and OpsRamp Software at HPE.

"It's becoming increasingly clear that for many, a combined approach, leveraging both APM and observability functionalities within a single, well-integrated tool, offers the most comprehensive solution for their monitoring and diagnostic requirements," confirms Arun Balachandran, Senior Product Marketing Manager, ManageEngine APM Solutions.

Ideally, organizations should aim for an integrated platform that combines both APM and observability, advises Menachem from ServiceNow. The objective isn't to accumulate more tools but to achieve deeper insights.

Andreas Grabner, Fellow DevRel and CNCF Ambassador, Dynatrace, agrees, "Ideally, organizations wouldn't need to manage separate tools. The most effective approach combines APM and observability into a single platform that provides unified data, context-rich insights, and automation. Fragmented tooling leads to data silos and slower issue resolution, while a converged platform improves visibility, collaboration, and time-to-value."

A unified platform serves as a single source of truth, streamlining resolution processes, enhancing accountability, and empowering informed decision-making across the board, Menachem from ServiceNow adds.

Integrated solutions can offer convenience, optimized operations and more robust performance for complex systems, Kunaparaju of HPE adds.

"Organizations increasingly recognize that they need unified platforms rather than point solutions," Rakesh Gupta, Head of Product Management at Observe points out. "The market is clearly moving toward consolidation, with 'single pane of glass' becoming a standard requirement from IT leadership."

There are tools that do both, but just as with any other tool purchase, you must weigh the pros and cons out there, warns Chrystal Taylor, Tech Evangelist at SolarWinds. There may be tools developed specifically for APM that have the benefit of greater maturity and feature sets that haven't been worked into observability tools out there. There may also be ways to integrate that data into your observability tools to get the best of both worlds. There are many options, so it's important to find the one best suited to your organization's needs and budget.

The trend is toward unified platforms that incorporate both capabilities, but organizations should evaluate their specific requirements before assuming one solution fits all, Paul Appleby, CEO of Virtana, concludes.

Observability with a Side of APM

Many of the experts recommend the tool combination in the form of a comprehensive Observability platform that includes APM among multiple other capabilities — and this concept further supports the view that APM is a subset of Observability, discussed in Part 3 of this series.

While some organizations choose to use both APM and Observability, it isn't a necessity, according to Emily Nakashima, VP of Engineering at Honeycomb. "Since APM is a subset of observability, organizations with a well-crafted observability strategy can utilize an observability tool to get everything APM offers and more."

"APM is just one part of the observability picture," explains Bahubali Shetti, Senior Director, Product Marketing, Elastic. "While APM focuses on identifying what's wrong within a specific service or set of services, observability helps you understand why by connecting signals across your entire environment using AI and machine learning. Full observability enables correlation of metrics, logs, and traces to uncover root causes, analyze patterns, and generate context-aware recommendations."

Shetti adds that with features like an AI Assistant, users can ask questions like, "Why is my checkout latency spiking?" and receive insights that automatically connect traces, logs, infrastructure metrics, and even internal knowledge like GitHub issues or support tickets. Observability also brings advanced capabilities like anomaly detection, pattern recognition, event categorization, and predictive analytics, allowing teams to move from reactive troubleshooting to proactive optimization. When combined with APM data, these capabilities deliver the end-to-end visibility and intelligence users need to resolve issues faster and scale systems more effectively.

"Both can co-exist, but for cost and complexity reasons, it is likely that organizations will move to the more encompassing observability approach," says Sven Delmas, VP of Research at Mezmo. "Note that an observability solution may or may not be just one tool."

Today organizations can expect to have APM in their observability tool but not necessarily vice versa, adds Hugo Kaczmarek, Director of Product, APM Suite at Datadog.

Keeping It Separate

Even though the experts recommend combining tools to get the best of both worlds, some organizations still rely on separate tools — whether due to legacy systems, departmental preferences, or unique functional requirements, says Balachandran from ManageEngine.

"And even the solutions that are a blend of both worlds — usually the result of acquired companies and merged toolsets — end up focusing on more of one than the other, with the lesser of the two simply there to provide context to the other or, worse, to be little more than box-checkers to pass an RFP," adds Leon Adato, Principal Technology Advocate, Catchpoint. "So companies probably will need both. More specifically, different teams within an organization will need the capabilities of one more than the other."

Unified Visibility and Actionable Insights

"What's most important is that organizations take a close look at what different tools and platforms offer and ensure that everything they require regarding APM/observability capabilities are met — whether that be through one tool, two tools, or five," says Cole from Tricentis.

Ultimately, the most important factor is ensuring that whichever tools are in place deliver unified visibility and actionable insights across the entire technology stack, from the application layer all the way down to the underlying infrastructure, recommends Balachandran from ManageEngine.

Start with: APM and Observability - Cutting Through the Confusion - Part 9, covering open source's impact on the evolution Observability.

Pete Goldin is Editor and Publisher of APMdigest

Hot Topics

The Latest

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

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ...