Skip to main content

Beyond the Perimeter: Why Application-Aware Network Monitoring Matters

Mark Troester
Progress

The modern world relies on applications: every business, regardless of industry, depends on them to varying degrees. Whether you operate a hospital, an e-commerce business, a farm or a factory, applications play a central role in day-to-day operations. Even a few minutes of application downtime can have disastrous consequences.

Consider this: according to a recent study, every minute of downtime costs businesses an average of $4,500, and outages typically last between 20 and 60 minutes. This means that at the very least, an outage can cost your company around $90,000 and potentially much more.

While most businesses focus on endpoint and perimeter protection to combat such incidents, there are many other factors that can disrupt an application beyond conventional perimeter breaches.

To effectively manage application experience (AX) and user experience (UX), businesses need greater visibility into the networks. This can be achieved through application-aware network performance monitoring (NPM) technologies.

How NPM Works

For many companies, application performance is a black box. They often become aware of issues only when complaints start pouring in, and even then, identifying the root cause can be time-consuming — a luxury most companies cannot afford.

NPM changes the game. It enables you to identify which applications are running below standard speed and measure response times for both the network and the application itself. This allows for quick differentiation between network delays and application delays when troubleshooting.

If the problem lies with the application, NPM provides IT teams with comprehensive information to resolve the issue. This includes response times for applications, transport times for the network, number of transactions, server response time, network transport time, responses in percentiles (maximum/minimum/average), number of concurrent users, and more.

Of course, not all applications require monitoring. NPM should be employed selectively, focusing on critical applications that are vital to daily business operations — such as customer-facing e-commerce applications. Additionally, it is crucial to integrate the information provided by NPM with the broader IT monitoring, management and surveillance ecosystem. In the realm of system security and operational efficiency, everything is interconnected.

NPM in Action

Let's consider a hypothetical scenario: you run a health insurance company. Thousands of users access your application daily to schedule doctor's appointments, make payments, and more. Suddenly seemingly out of nowhere, the application stops functioning. Complaints and calls flood in, and people are understandably frantic—after all, healthcare is of utmost importance.

At this point, many IT departments initiate the blame game or start grasping blindly for answers they know they may not find. However, with NPM in place, the next step is simple: consult the list.

What is the list? NPM solutions measure the response times and delays for every user-to-app transaction, aggregating them into a sortable list from slowest to fastest. This means that IT can swiftly identify the root cause of the problem and take immediate action to find a solution.

In 2023, seamlessness has become a basic consumer expectation. When a consumer places an online order, they expect to have the option of receiving it within a day or two. When they request a car, they expect it to arrive within minutes. And when they open an app, they expect it to launch within seconds — no more than one or two. Exceeding this threshold puts your company's reputation at stake. By implementing NPM, businesses can ensure that when application issues arise, they can promptly rectify them, keeping customers satisfied and preventing more severe consequences.

Mark Troester is VP of Strategy at Progress

Hot Topics

The Latest

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...

Technology leaders across the federal landscape are facing, and will continue to face, an uphill battle when it comes to fortifying their digital environments against hostile and persistent threat actors. On one hand, they are being asked to push digital transformation ... On the other hand, they are facing the fiscal uncertainty of continuing resolutions (CR) and government shutdowns looming near and far. In the face of these challenges, CIOs, CTOs, and CISOs must figure out how to modernize legacy systems and infrastructure while doing more with less and still defending against external and internal threats ...

Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...

In the world of digital-first business, there is no tolerance for service outages. Businesses know that outages are the quickest way to lose money and customers. For smaller organizations, unplanned downtime could even force the business to close ... A new study from PagerDuty, The State of AI-First Operations, reveals that companies actively incorporating AI into operations now view operational resilience as a growth driver rather than a cost center. But how are they achieving it? ...

In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Beyond the Perimeter: Why Application-Aware Network Monitoring Matters

Mark Troester
Progress

The modern world relies on applications: every business, regardless of industry, depends on them to varying degrees. Whether you operate a hospital, an e-commerce business, a farm or a factory, applications play a central role in day-to-day operations. Even a few minutes of application downtime can have disastrous consequences.

Consider this: according to a recent study, every minute of downtime costs businesses an average of $4,500, and outages typically last between 20 and 60 minutes. This means that at the very least, an outage can cost your company around $90,000 and potentially much more.

While most businesses focus on endpoint and perimeter protection to combat such incidents, there are many other factors that can disrupt an application beyond conventional perimeter breaches.

To effectively manage application experience (AX) and user experience (UX), businesses need greater visibility into the networks. This can be achieved through application-aware network performance monitoring (NPM) technologies.

How NPM Works

For many companies, application performance is a black box. They often become aware of issues only when complaints start pouring in, and even then, identifying the root cause can be time-consuming — a luxury most companies cannot afford.

NPM changes the game. It enables you to identify which applications are running below standard speed and measure response times for both the network and the application itself. This allows for quick differentiation between network delays and application delays when troubleshooting.

If the problem lies with the application, NPM provides IT teams with comprehensive information to resolve the issue. This includes response times for applications, transport times for the network, number of transactions, server response time, network transport time, responses in percentiles (maximum/minimum/average), number of concurrent users, and more.

Of course, not all applications require monitoring. NPM should be employed selectively, focusing on critical applications that are vital to daily business operations — such as customer-facing e-commerce applications. Additionally, it is crucial to integrate the information provided by NPM with the broader IT monitoring, management and surveillance ecosystem. In the realm of system security and operational efficiency, everything is interconnected.

NPM in Action

Let's consider a hypothetical scenario: you run a health insurance company. Thousands of users access your application daily to schedule doctor's appointments, make payments, and more. Suddenly seemingly out of nowhere, the application stops functioning. Complaints and calls flood in, and people are understandably frantic—after all, healthcare is of utmost importance.

At this point, many IT departments initiate the blame game or start grasping blindly for answers they know they may not find. However, with NPM in place, the next step is simple: consult the list.

What is the list? NPM solutions measure the response times and delays for every user-to-app transaction, aggregating them into a sortable list from slowest to fastest. This means that IT can swiftly identify the root cause of the problem and take immediate action to find a solution.

In 2023, seamlessness has become a basic consumer expectation. When a consumer places an online order, they expect to have the option of receiving it within a day or two. When they request a car, they expect it to arrive within minutes. And when they open an app, they expect it to launch within seconds — no more than one or two. Exceeding this threshold puts your company's reputation at stake. By implementing NPM, businesses can ensure that when application issues arise, they can promptly rectify them, keeping customers satisfied and preventing more severe consequences.

Mark Troester is VP of Strategy at Progress

Hot Topics

The Latest

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...

Technology leaders across the federal landscape are facing, and will continue to face, an uphill battle when it comes to fortifying their digital environments against hostile and persistent threat actors. On one hand, they are being asked to push digital transformation ... On the other hand, they are facing the fiscal uncertainty of continuing resolutions (CR) and government shutdowns looming near and far. In the face of these challenges, CIOs, CTOs, and CISOs must figure out how to modernize legacy systems and infrastructure while doing more with less and still defending against external and internal threats ...

Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...

In the world of digital-first business, there is no tolerance for service outages. Businesses know that outages are the quickest way to lose money and customers. For smaller organizations, unplanned downtime could even force the business to close ... A new study from PagerDuty, The State of AI-First Operations, reveals that companies actively incorporating AI into operations now view operational resilience as a growth driver rather than a cost center. But how are they achieving it? ...

In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...