Assuring Exceptional Experiences with Applications Requires Assuring Network Performance - Part 1

Nadeem Zahid
cPacket Networks
Learn more about cPacket Networks

Network Performance Management and Diagnostics is an important aspect of Application Performance Management because application performance and experiences are intertwined with network performance. Networks connect end-users with applications; they also connect application components such as application servers and database servers, microservices, and IoT devices.

Experiences with enterprise and web-based (SaaS) applications by internal and external end-users directly impact an organization's success. These experiences may be formally specified with measurable metrics (for example, payment transaction response times) in a Service Level Experience (SLE). Externally, experiences impact customer satisfaction, retention and lifetime value. Within the organization, experiences affect employee satisfaction and productivity, including IT efficiency. Experiences also matter to automated processes, especially when specific timing tolerances are critical. Therefore, assuring exceptional experiences for all stakeholders and use cases is a critical success factor.


Frustration sets in for end-users who experience issues that are not proactively addressed. Customers may choose a competing service and internal customers will be less productive, resulting in a negative impact to the organization's top and bottom lines. IT personnel also get frustrated while troubleshooting and resolving issues under pressure. Proactively assuring performance using predictive and prescriptive analytics driven by data from monitoring is the ideal way to assure experiences because it averts poor experiences as well as time-consuming, costly and frustrating troubleshooting and problem solving.

Experiences with applications that are directly impacted by network performance can be grouped into the following three high-level categories:

■ Connectivity determines whether end-users and other processes including automation can access an application.

■ Responsiveness is either a quantitative or subjective measure of acceptability of the interactions with an application. For example, a target of receiving a response within one second is acceptable for many use cases.

■ Quality is another quantitative or subjective measure of acceptability. For example, a videoconference session that has delays, dropouts and other noticeable issues would be rated as poor quality.

Assuring Exceptional Experiences are Driving Performance Upgrades

High performance is often the way to assure responsiveness and quality. High performance often means increased processing speed that is reliant on data transmission speed, especially for processing intensive applications and streaming applications. Network throughput rates increase in steps. Currently the typical data rates are 10Gbps, 40Gbps, and 100Gbps. The need for performance and hence speed is driving upgrades of data center network data rates and corresponding monitoring to operate at 100Gbps.

High fidelity visibility and observability of the IT system's performance metrics are needed to manage and maximize user experiences. As data center networks continue migrating to 100Gbps data rates, monitoring resolution must keep pace.

Finding the Root Cause of Experience Issues

Customer support and IT help desks receive trouble tickets when performance issues occur. Tickets initiate an effort to resolve issues and start a timer that measures the mean time to resolution (MTTR) - a common metric used to gauge IT performance. Maintaining a low MTTR is a direct indicator of IT effectiveness and efficiency and an indirect indicator of customer satisfaction. The typical next steps include escalating the issue to specific roles and personnel within the IT team to isolate the root cause by first determining whether the problem is with the network or the application.

Investigating requires analyzing specific observable network and application behaviors and metrics. There are several entities and links between an end-user and an application that could cause connectivity issues if they malfunction. These include: the end-user's device, one or more networks (i.e., WAN, LAN, WLAN, DCN), the servers and other IT infrastructure hosting the application, and the application itself including underlying microservices and other software components.

Connectivity Issues

Let's look at a situation where network connectivity is inhibiting an employee's ability to access a custom application running within an organization's data center. The inability to access the application could be caused by a malfunction of the following connectivity stages:

■ Identity and Access Management

■ DHCP

■ DNS

■ Connectivity with the application server(s)

In such cases, investigator(s) should look at observable health and performance metrics in hopes of quickly isolating the problem. Using event logs, Ping, and Internet Control Message Protocol are quick ways to discover the root cause of connectivity issues. If no problems are found, the investigator(s) can dig deeper by analyzing network packet data to examine observed traffic and SYN/SYN ACK errors to determine if exchanges including TCP/IP handshakes at each of the connectivity stages listed above are working properly.

Go to: Assuring Exceptional Experiences with Applications Requires Assuring Network Performance - Part 2.

Nadeem Zahid is VP of Product Management & Marketing at cPacket Networks

Related Links

Hot Topics

Related Vendors

The Latest

Keys to Building a Partner Ecosystem That Scales

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

How AI Agents Are Reshaping DataOps for the Always-On Enterprise

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

AI Deepfakes: Rethinking Trust in the Workplace

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Nine in Ten Enterprises Plan Cloud Data Repatriation amid Rising Cloud Costs and Data Sovereignty Mandates

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Why ITOps Need Right-Sized AI, Not Bigger Models

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

The End of Reactive DevOps: AI-Driven Observability for Zero-Defect Digital Systems

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

5 Takeaways from the Observability Forecast for Media and Entertainment

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Why Moving Off the Cloud Is the Easy Part and What Comes Next Is Where Things Get Hard

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

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

Assuring Exceptional Experiences with Applications Requires Assuring Network Performance - Part 1

Nadeem Zahid
cPacket Networks
Learn more about cPacket Networks

Network Performance Management and Diagnostics is an important aspect of Application Performance Management because application performance and experiences are intertwined with network performance. Networks connect end-users with applications; they also connect application components such as application servers and database servers, microservices, and IoT devices.

Experiences with enterprise and web-based (SaaS) applications by internal and external end-users directly impact an organization's success. These experiences may be formally specified with measurable metrics (for example, payment transaction response times) in a Service Level Experience (SLE). Externally, experiences impact customer satisfaction, retention and lifetime value. Within the organization, experiences affect employee satisfaction and productivity, including IT efficiency. Experiences also matter to automated processes, especially when specific timing tolerances are critical. Therefore, assuring exceptional experiences for all stakeholders and use cases is a critical success factor.


Frustration sets in for end-users who experience issues that are not proactively addressed. Customers may choose a competing service and internal customers will be less productive, resulting in a negative impact to the organization's top and bottom lines. IT personnel also get frustrated while troubleshooting and resolving issues under pressure. Proactively assuring performance using predictive and prescriptive analytics driven by data from monitoring is the ideal way to assure experiences because it averts poor experiences as well as time-consuming, costly and frustrating troubleshooting and problem solving.

Experiences with applications that are directly impacted by network performance can be grouped into the following three high-level categories:

■ Connectivity determines whether end-users and other processes including automation can access an application.

■ Responsiveness is either a quantitative or subjective measure of acceptability of the interactions with an application. For example, a target of receiving a response within one second is acceptable for many use cases.

■ Quality is another quantitative or subjective measure of acceptability. For example, a videoconference session that has delays, dropouts and other noticeable issues would be rated as poor quality.

Assuring Exceptional Experiences are Driving Performance Upgrades

High performance is often the way to assure responsiveness and quality. High performance often means increased processing speed that is reliant on data transmission speed, especially for processing intensive applications and streaming applications. Network throughput rates increase in steps. Currently the typical data rates are 10Gbps, 40Gbps, and 100Gbps. The need for performance and hence speed is driving upgrades of data center network data rates and corresponding monitoring to operate at 100Gbps.

High fidelity visibility and observability of the IT system's performance metrics are needed to manage and maximize user experiences. As data center networks continue migrating to 100Gbps data rates, monitoring resolution must keep pace.

Finding the Root Cause of Experience Issues

Customer support and IT help desks receive trouble tickets when performance issues occur. Tickets initiate an effort to resolve issues and start a timer that measures the mean time to resolution (MTTR) - a common metric used to gauge IT performance. Maintaining a low MTTR is a direct indicator of IT effectiveness and efficiency and an indirect indicator of customer satisfaction. The typical next steps include escalating the issue to specific roles and personnel within the IT team to isolate the root cause by first determining whether the problem is with the network or the application.

Investigating requires analyzing specific observable network and application behaviors and metrics. There are several entities and links between an end-user and an application that could cause connectivity issues if they malfunction. These include: the end-user's device, one or more networks (i.e., WAN, LAN, WLAN, DCN), the servers and other IT infrastructure hosting the application, and the application itself including underlying microservices and other software components.

Connectivity Issues

Let's look at a situation where network connectivity is inhibiting an employee's ability to access a custom application running within an organization's data center. The inability to access the application could be caused by a malfunction of the following connectivity stages:

■ Identity and Access Management

■ DHCP

■ DNS

■ Connectivity with the application server(s)

In such cases, investigator(s) should look at observable health and performance metrics in hopes of quickly isolating the problem. Using event logs, Ping, and Internet Control Message Protocol are quick ways to discover the root cause of connectivity issues. If no problems are found, the investigator(s) can dig deeper by analyzing network packet data to examine observed traffic and SYN/SYN ACK errors to determine if exchanges including TCP/IP handshakes at each of the connectivity stages listed above are working properly.

Go to: Assuring Exceptional Experiences with Applications Requires Assuring Network Performance - Part 2.

Nadeem Zahid is VP of Product Management & Marketing at cPacket Networks

Related Links

Hot Topics

Related Vendors

The Latest

Keys to Building a Partner Ecosystem That Scales

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

How AI Agents Are Reshaping DataOps for the Always-On Enterprise

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

AI Deepfakes: Rethinking Trust in the Workplace

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Nine in Ten Enterprises Plan Cloud Data Repatriation amid Rising Cloud Costs and Data Sovereignty Mandates

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Why ITOps Need Right-Sized AI, Not Bigger Models

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

The End of Reactive DevOps: AI-Driven Observability for Zero-Defect Digital Systems

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

5 Takeaways from the Observability Forecast for Media and Entertainment

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Why Moving Off the Cloud Is the Easy Part and What Comes Next Is Where Things Get Hard

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

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