Skip to main content

10 Questions to Ask When Evaluating Network Performance Management Solutions - Part 1

Jay Botelho

Network performance is one of the most critical aspects of successful business operations. Effective network performance enables internal and external communication between various company locations, as well as clients and partners — imperative in today's dispersed workforce. When networks do not perform well and experience malfunctions and failures, companies face disruptions and loss of business continuity. Understanding how efficiently and effectively a network performs helps mitigate these issues, leading to increased productivity and profitability.

Successful insight into the performance of a company's networks starts with effective network performance management (NPM) tools. However, with the plethora of options it can be overwhelming for IT teams to choose the right one. Here are 10 essential questions to ask before selecting an NPM tool.

Question #1: Does the solution provide comprehensive End-to-end visibility?

With today's digital landscape, network management solutions must support a high-performance digital experience and deliver comprehensive, application-focused analysis, processing data from many locations, including routers, firewalls, and more. It also must be able to alert on network and application-performance issues anywhere in the network path, displaying these alerts as part of the end-to-end flow map which helps find the root cause of issues more quickly.

A modern NPM solution must provide correlated information from the entire network, including complex, hybrid environments.

Question #2: Does your solution provide visibility into SD-WAN?

As organizations become increasingly distributed, many look to SD-WAN for better communications and lower costs. This makes SD-WAN a critical element in your network infrastructure, and one which must be factored into your end-to-end network visibility.

SD-WAN has a direct impact on network routing, and therefore on network latencies, so it's essential to ensure that SD-WAN is delivering the expected benefits from a network, security, and cost perspective. The dynamic nature of SD-WAN puts additional pressure on network performance monitoring, so be sure the NPM solution can easily track and visualize any WAN routing changes.

Question #3: Is cloud monitoring supported?

"Cloud" can mean different things to different organizations, but whether it's corporate applications in a hosted private cloud, full-on public cloud, or SaaS applications, the NPM solution must be able to monitor and visualize it, end-to-end. This may require the use of additional modules, and sometimes even proprietary features of the cloud provider, so it's important to determine up front both if, and how, the NPM solution will provide the end-to-end visibility you need to eliminate the blind spots that are common once applications are moved to the Cloud.

Question #4: Does the solution provide comprehensive application monitoring and optimization?

Optimized application performance is critical to business efficiency, yet optimization is becoming more complex as core business functions are moved out of the data center and distributed across multiple service and application providers. Legacy NPM solutions often lack the visibility needed to even monitor, much less optimize, these highly distributed applications.

To address this complexity, a network performance monitoring solution should tackle these three essential functions: application visibility, network optimization, and application performance assessment. It must address application performance within the context of network infrastructure metrics, since the applications do nothing useful without the network. Application performance can only be optimized when built on a solid network foundation, and an effective NPM solution must provide visibility into both.

Question #5: Does the solution provide insights into voice and video applications?

Gone are the days when voice and video ran on their own, expensive networks. Voice and video are now just other applications running on the network, and given their real-time nature, they are some of the most demanding applications. Both voice and video are extremely sensitive to network latency and packet loss. Voice and video traffic is useless if it's delayed more than a few hundred milliseconds, so voice and video traffic must be tagged and given priority on the network for these applications to work effectively.

If voice or video traffic is degraded, the source of that degradation is often network latency, so it's imperative that the NPM solution be able to visualize the traffic end-to-end, and quickly identify specific network hops that are introducing latency. The solution must also be able to analyze and report on the priority tagging of voice and video packets, called QoS (Quality of Service), and identify areas where QoS is not properly configured. And as a bonus, the solution should be able to correct QoS configuration issues to quickly restore the quality of voice and video communications.

Go to: 10 Questions to Ask When Evaluating Network Performance Management Solutions - Part 2

Hot Topics

The Latest

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...

Applications have long used bounded, deterministic logic to control what happens within their own functions. Process orchestration coordinates activity across people, applications, decisions, and automation tools. Workload orchestration coordinates executable work and dependencies across applications, platforms, and infrastructure. As agentic capabilities enter applications and domain systems, more planning and decision-making will also occur inside those environments. These forms of automation will coexist. Sometimes they will overlap, and they will increasingly need to exchange triggers, state, and results. But they are not becoming interchangeable ...

For many organizations, the AI agenda has landed squarely on the CIO's desk. At first glance, that makes perfect sense. AI depends on data, infrastructure, security, integration, governance and scalable technology platforms — all areas where the CIO plays a central role. But there is a problem with treating AI primarily as an IT initiative: AI is not simply a technology deployment. It’s also a business transformation ...

In MEAN TIME TO INSIGHT Episode 28, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and special guest Sanjay Gidwani, Founder & CEO of Kosmos AI Labs, discuss root cause analysis ... 

A gap is growing between how quickly organizations are putting AI to work and how much autonomy they are prepared to give it, according to The 2026 State of Observability Report from Grafana Labs ...

AI agents and agentic browsers now make up a growing share of the traffic reaching websites and applications. They search, compare, sign up, and increasingly complete purchases on behalf of the people who delegate those tasks. Digital experience monitoring (DEM) was built on the assumption that every session is performed by a person. That assumption no longer holds, and the measurements built on it are shifting without notice ...

Who is watching the watcher? This may not be the first question that comes up when discussing AI observability but sooner or later you start to wonder. Part 12 covers the dilemma of AI monitoring AI ...

Two AI agents got caught in a loop with each other over a weekend and racked up $47,000 in charges, according to John D'Emic, CTO of Revenium. No alert fired because nothing "broke." Stories like this are why cost has become one of the most pressing questions in AI observability. Traditional monitoring was built to catch failures, not wasted spend, and AI systems can burn through budget while every dashboard stays green. Part 11 explores how AI observability relates to AI cost management, and whether they are one discipline or two ...

10 Questions to Ask When Evaluating Network Performance Management Solutions - Part 1

Jay Botelho

Network performance is one of the most critical aspects of successful business operations. Effective network performance enables internal and external communication between various company locations, as well as clients and partners — imperative in today's dispersed workforce. When networks do not perform well and experience malfunctions and failures, companies face disruptions and loss of business continuity. Understanding how efficiently and effectively a network performs helps mitigate these issues, leading to increased productivity and profitability.

Successful insight into the performance of a company's networks starts with effective network performance management (NPM) tools. However, with the plethora of options it can be overwhelming for IT teams to choose the right one. Here are 10 essential questions to ask before selecting an NPM tool.

Question #1: Does the solution provide comprehensive End-to-end visibility?

With today's digital landscape, network management solutions must support a high-performance digital experience and deliver comprehensive, application-focused analysis, processing data from many locations, including routers, firewalls, and more. It also must be able to alert on network and application-performance issues anywhere in the network path, displaying these alerts as part of the end-to-end flow map which helps find the root cause of issues more quickly.

A modern NPM solution must provide correlated information from the entire network, including complex, hybrid environments.

Question #2: Does your solution provide visibility into SD-WAN?

As organizations become increasingly distributed, many look to SD-WAN for better communications and lower costs. This makes SD-WAN a critical element in your network infrastructure, and one which must be factored into your end-to-end network visibility.

SD-WAN has a direct impact on network routing, and therefore on network latencies, so it's essential to ensure that SD-WAN is delivering the expected benefits from a network, security, and cost perspective. The dynamic nature of SD-WAN puts additional pressure on network performance monitoring, so be sure the NPM solution can easily track and visualize any WAN routing changes.

Question #3: Is cloud monitoring supported?

"Cloud" can mean different things to different organizations, but whether it's corporate applications in a hosted private cloud, full-on public cloud, or SaaS applications, the NPM solution must be able to monitor and visualize it, end-to-end. This may require the use of additional modules, and sometimes even proprietary features of the cloud provider, so it's important to determine up front both if, and how, the NPM solution will provide the end-to-end visibility you need to eliminate the blind spots that are common once applications are moved to the Cloud.

Question #4: Does the solution provide comprehensive application monitoring and optimization?

Optimized application performance is critical to business efficiency, yet optimization is becoming more complex as core business functions are moved out of the data center and distributed across multiple service and application providers. Legacy NPM solutions often lack the visibility needed to even monitor, much less optimize, these highly distributed applications.

To address this complexity, a network performance monitoring solution should tackle these three essential functions: application visibility, network optimization, and application performance assessment. It must address application performance within the context of network infrastructure metrics, since the applications do nothing useful without the network. Application performance can only be optimized when built on a solid network foundation, and an effective NPM solution must provide visibility into both.

Question #5: Does the solution provide insights into voice and video applications?

Gone are the days when voice and video ran on their own, expensive networks. Voice and video are now just other applications running on the network, and given their real-time nature, they are some of the most demanding applications. Both voice and video are extremely sensitive to network latency and packet loss. Voice and video traffic is useless if it's delayed more than a few hundred milliseconds, so voice and video traffic must be tagged and given priority on the network for these applications to work effectively.

If voice or video traffic is degraded, the source of that degradation is often network latency, so it's imperative that the NPM solution be able to visualize the traffic end-to-end, and quickly identify specific network hops that are introducing latency. The solution must also be able to analyze and report on the priority tagging of voice and video packets, called QoS (Quality of Service), and identify areas where QoS is not properly configured. And as a bonus, the solution should be able to correct QoS configuration issues to quickly restore the quality of voice and video communications.

Go to: 10 Questions to Ask When Evaluating Network Performance Management Solutions - Part 2

Hot Topics

The Latest

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...

Applications have long used bounded, deterministic logic to control what happens within their own functions. Process orchestration coordinates activity across people, applications, decisions, and automation tools. Workload orchestration coordinates executable work and dependencies across applications, platforms, and infrastructure. As agentic capabilities enter applications and domain systems, more planning and decision-making will also occur inside those environments. These forms of automation will coexist. Sometimes they will overlap, and they will increasingly need to exchange triggers, state, and results. But they are not becoming interchangeable ...

For many organizations, the AI agenda has landed squarely on the CIO's desk. At first glance, that makes perfect sense. AI depends on data, infrastructure, security, integration, governance and scalable technology platforms — all areas where the CIO plays a central role. But there is a problem with treating AI primarily as an IT initiative: AI is not simply a technology deployment. It’s also a business transformation ...

In MEAN TIME TO INSIGHT Episode 28, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and special guest Sanjay Gidwani, Founder & CEO of Kosmos AI Labs, discuss root cause analysis ... 

A gap is growing between how quickly organizations are putting AI to work and how much autonomy they are prepared to give it, according to The 2026 State of Observability Report from Grafana Labs ...

AI agents and agentic browsers now make up a growing share of the traffic reaching websites and applications. They search, compare, sign up, and increasingly complete purchases on behalf of the people who delegate those tasks. Digital experience monitoring (DEM) was built on the assumption that every session is performed by a person. That assumption no longer holds, and the measurements built on it are shifting without notice ...

Who is watching the watcher? This may not be the first question that comes up when discussing AI observability but sooner or later you start to wonder. Part 12 covers the dilemma of AI monitoring AI ...

Two AI agents got caught in a loop with each other over a weekend and racked up $47,000 in charges, according to John D'Emic, CTO of Revenium. No alert fired because nothing "broke." Stories like this are why cost has become one of the most pressing questions in AI observability. Traditional monitoring was built to catch failures, not wasted spend, and AI systems can burn through budget while every dashboard stays green. Part 11 explores how AI observability relates to AI cost management, and whether they are one discipline or two ...