Skip to main content

The Pros & Cons of Flow & Packet Data - Part 2

Jay Botelho

What are the cons or challenges of Flow and Packet data?

Start with: The Pros and Cons of Flow and Packet Data - Part 1

While Flow data offers a high level of traffic visibility, it has little detail about what's actually flowing. For example, you can't see microbursts, or the amount of time an application spends churning on a request. It can also present complications for flow monitoring at the edge (small, remote offices), since many edge routers aren't full-featured enough to offer xFlow.

And although xFlow come "for free," it does put an extra processing load on the router, especially when the router is very busy, and this can lead to gaps in visibility when you need it most.

Finally, flow sampling is sometimes used to reduce the processing load on the router, making security detection much less effective since some flows, and perhaps the flows in question, may not be reported on due to sampling.

When it comes to Packet data, dedicated hardware and cabling are required between mirror ports on a router and a DPI application or appliance. This means there's more equipment to purchase, configure and maintain. Furthermore, when routers get busy the processing power required to mirror data can be reduced, resuling in some data not being mirrored, thereby reducing the effectiveness of the mirrored data. This can be addressed by using network taps or packet brokers, but this introduces even more hardware into the solution.

Packet data also requires specialized tools for analysis and a high level of expertise to be used effectively. To reap the benefits of packet data, organizations need to invest in solutions like protocol analyzers and have NetOps teams that understand how to use them. It also adds more complexity to network management, as network engineers need to be very aware of what data they want to monitor, and then ensure that the data mirroring they originally configure remains relevant as other network changes are made.

And the use of HTTPS and VPNs that create privacy tunneling is making packet payload analysis more challenging, often limited to specific instances where the keys for decryption are known for specific network flows.

What are some common ways to use Flow and Packet data to troubleshoot network performance?

The more complex underlying network problems are, the more sleuthing and expertise in protocol and packet analysis are needed. End-to-end visibility extrapolated from Flow and Packet data aids network troubleshooting at the most critical levels and sets the stage for further monitoring integrations that track application performance and sophisticated user experiences.

By using network monitoring solutions (like NPMD and NDR), finding the answers to common issues can be simplified. Here are four ways Packet and Flow data can help.

Topological Views

These views use Flow and Packet data to provide a comprehensive map of network performance. This helps Netops teams to identify infrastructure components in need of upgrading or replacement, and perform capacity planning. They also help when maintaining a real-time comprehensive device inventory, can trigger automatic device discovery, can help to proactively identify choke points on the network, and can be used to compare different performance metrics.

Flow Path Analysis

This is used to identify possible routes, hops, and network latency impacts across endpoints based on IP address. Packet and flow data allows Netops to identify issues caused by load balancing and to identify other issues caused by routing, such as sudden changes in network latency and poor performance of real-time protocols, typically voice and video.

Application Monitoring

Establishing performance baselines that can be used to monitor for abnormal traffic levels is crucial for application performance. Flow and Packet data allows NetOps to uncover insight into how the network is being used at the application level. For example, by identifying policy weaknesses that have allowed unwanted usage.

Intrusion Detection and Prevention Monitoring

Having insight into Flow and Packet data allows NetOps and SecOps to identify a known attack or type of attack based on its signature (signature-based). Teams can also identify deviations from the norm of network behaviors (anomaly-based) or the norms of protocol use (stateful protocol analysis).

Oftentimes, enterprises have seen Flow and Packet data as mutually exclusive — that one can be utilized without the need for the other — but the truth is that when combined NetOps teams can gain more complete visibility. This helps to protect against security threats, investigate alerts and ensure the overall performance of the network and applications.

Hot Topics

The Latest

"AI readiness" has quickly become one of the defining priorities of the modern enterprise. Business decision makers across virtually every industry are working to build roadmaps, solidify strategies, and set expectations around technological investment and adoption. However, at the very same time these leaders are laying their plans, the state of AI continues to change and shift beneath their feet. This raises a fundamental question about the notion of AI readiness: what is it we're actually getting ready for? ...

Genpact and HFS Research recently found that 92% of senior executives at Global 2000 companies believe agentic AI will fundamentally change how work gets done. Yet 85% of them also recognize enterprise debt as a factor limiting their AI value. To move beyond pilots and deliver tangible value, CIOs need to address enterprise debt — the accumulated operational drag from outdated technology, fragmented data, inefficient processes, and talent gaps ...

Proactive is going to become the default expectation, not a nice-to-have. Predicting problems before they happen and fixing them ahead of time will become table stakes, especially for smaller teams and MSPs who cannot afford a big NOC staff ...

The final two installments of the series, Exploring AI Observability, cover predictions from the experts about where AI observability is heading ... In the next few years, tracking your AI won't just be a nice-to-have tool, it will be a survival requirement for businesses ...

Cloud absolutely changed IT for the better. But after more than a decade of using it, companies have also learned something else. Where an application runs matters, and there isn't one environment that makes sense for everything ...

Automation often starts with the people closest to an immediate need. A developer may schedule a script with cron or Amazon EventBridge Scheduler; a business team may adopt an RPA bot, low-code platform, or agent. Many tools stay useful within one domain. Some become consequential across organizational boundaries because other systems and teams depend on them or business outcomes rely on their timing and recovery. Those cases may call for broader coordination ...

The conventional wisdom in our industry says that AI demands a new operating model and specific data tailored for it. I disagree. AI is changing the rules, but not in the way people think ...

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

The Pros & Cons of Flow & Packet Data - Part 2

Jay Botelho

What are the cons or challenges of Flow and Packet data?

Start with: The Pros and Cons of Flow and Packet Data - Part 1

While Flow data offers a high level of traffic visibility, it has little detail about what's actually flowing. For example, you can't see microbursts, or the amount of time an application spends churning on a request. It can also present complications for flow monitoring at the edge (small, remote offices), since many edge routers aren't full-featured enough to offer xFlow.

And although xFlow come "for free," it does put an extra processing load on the router, especially when the router is very busy, and this can lead to gaps in visibility when you need it most.

Finally, flow sampling is sometimes used to reduce the processing load on the router, making security detection much less effective since some flows, and perhaps the flows in question, may not be reported on due to sampling.

When it comes to Packet data, dedicated hardware and cabling are required between mirror ports on a router and a DPI application or appliance. This means there's more equipment to purchase, configure and maintain. Furthermore, when routers get busy the processing power required to mirror data can be reduced, resuling in some data not being mirrored, thereby reducing the effectiveness of the mirrored data. This can be addressed by using network taps or packet brokers, but this introduces even more hardware into the solution.

Packet data also requires specialized tools for analysis and a high level of expertise to be used effectively. To reap the benefits of packet data, organizations need to invest in solutions like protocol analyzers and have NetOps teams that understand how to use them. It also adds more complexity to network management, as network engineers need to be very aware of what data they want to monitor, and then ensure that the data mirroring they originally configure remains relevant as other network changes are made.

And the use of HTTPS and VPNs that create privacy tunneling is making packet payload analysis more challenging, often limited to specific instances where the keys for decryption are known for specific network flows.

What are some common ways to use Flow and Packet data to troubleshoot network performance?

The more complex underlying network problems are, the more sleuthing and expertise in protocol and packet analysis are needed. End-to-end visibility extrapolated from Flow and Packet data aids network troubleshooting at the most critical levels and sets the stage for further monitoring integrations that track application performance and sophisticated user experiences.

By using network monitoring solutions (like NPMD and NDR), finding the answers to common issues can be simplified. Here are four ways Packet and Flow data can help.

Topological Views

These views use Flow and Packet data to provide a comprehensive map of network performance. This helps Netops teams to identify infrastructure components in need of upgrading or replacement, and perform capacity planning. They also help when maintaining a real-time comprehensive device inventory, can trigger automatic device discovery, can help to proactively identify choke points on the network, and can be used to compare different performance metrics.

Flow Path Analysis

This is used to identify possible routes, hops, and network latency impacts across endpoints based on IP address. Packet and flow data allows Netops to identify issues caused by load balancing and to identify other issues caused by routing, such as sudden changes in network latency and poor performance of real-time protocols, typically voice and video.

Application Monitoring

Establishing performance baselines that can be used to monitor for abnormal traffic levels is crucial for application performance. Flow and Packet data allows NetOps to uncover insight into how the network is being used at the application level. For example, by identifying policy weaknesses that have allowed unwanted usage.

Intrusion Detection and Prevention Monitoring

Having insight into Flow and Packet data allows NetOps and SecOps to identify a known attack or type of attack based on its signature (signature-based). Teams can also identify deviations from the norm of network behaviors (anomaly-based) or the norms of protocol use (stateful protocol analysis).

Oftentimes, enterprises have seen Flow and Packet data as mutually exclusive — that one can be utilized without the need for the other — but the truth is that when combined NetOps teams can gain more complete visibility. This helps to protect against security threats, investigate alerts and ensure the overall performance of the network and applications.

Hot Topics

The Latest

"AI readiness" has quickly become one of the defining priorities of the modern enterprise. Business decision makers across virtually every industry are working to build roadmaps, solidify strategies, and set expectations around technological investment and adoption. However, at the very same time these leaders are laying their plans, the state of AI continues to change and shift beneath their feet. This raises a fundamental question about the notion of AI readiness: what is it we're actually getting ready for? ...

Genpact and HFS Research recently found that 92% of senior executives at Global 2000 companies believe agentic AI will fundamentally change how work gets done. Yet 85% of them also recognize enterprise debt as a factor limiting their AI value. To move beyond pilots and deliver tangible value, CIOs need to address enterprise debt — the accumulated operational drag from outdated technology, fragmented data, inefficient processes, and talent gaps ...

Proactive is going to become the default expectation, not a nice-to-have. Predicting problems before they happen and fixing them ahead of time will become table stakes, especially for smaller teams and MSPs who cannot afford a big NOC staff ...

The final two installments of the series, Exploring AI Observability, cover predictions from the experts about where AI observability is heading ... In the next few years, tracking your AI won't just be a nice-to-have tool, it will be a survival requirement for businesses ...

Cloud absolutely changed IT for the better. But after more than a decade of using it, companies have also learned something else. Where an application runs matters, and there isn't one environment that makes sense for everything ...

Automation often starts with the people closest to an immediate need. A developer may schedule a script with cron or Amazon EventBridge Scheduler; a business team may adopt an RPA bot, low-code platform, or agent. Many tools stay useful within one domain. Some become consequential across organizational boundaries because other systems and teams depend on them or business outcomes rely on their timing and recovery. Those cases may call for broader coordination ...

The conventional wisdom in our industry says that AI demands a new operating model and specific data tailored for it. I disagree. AI is changing the rules, but not in the way people think ...

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