Keeping Digital Business Running
Network Performance Management for Digital Operations
September 22, 2016

Jim Frey
Kentik

Share this

The importance of digital business operations is now a given, and for good reason. Recently, Pandora announced that it was launching a subscription service and lowering monthly fees, which means that the already huge percentage of its revenues driven by advertising is going to have to increase in order to maintain the top line. It goes without saying that streaming music, like many other ad-driven business models, relies critically on user experience, and user experience relies critically on network performance. So much so that streaming media, gaming and many other such digital service providers have built private CDNs to guarantee that app and ad bits make it to user eyes and ears in a very timely and reliable fashion.

Network performance monitoring (NPM) has been around a long time. Unlike APM, NPM is still in the process of catching up to cloud realities. In May of this year, Gartner analyst Sanjit Ganguli published a research note entitled Network Performance Monitoring Tools Leave Gaps in Cloud Monitoring. It's a fairly biting critique of the NPM space that says, essentially, that the vast majority of current NPM approaches were largely built for a pre-cloud era, and are unable to adapt because of the new complexities brought by decentralization and full stack virtualization. As a result, network managers are left in the lurch when trying to adapt to the realities of digital operations.

NPM had its origins in open-source manual tools such as MRTG, Nagios, and Wireshark, which are still widely available and useful. However, on a commercial basis, traditional NPM approaches came about during the rise of centralized, private enterprise data centers connected by networks that were built to reach campuses and branch offices across an outsourced, yet essentially private IP/MPLS WAN. Applications of this era were developed in a relatively monolithic fashion. This overall architecture meant that there a few, well defined traffic aggregation points, such as the juncture between LAN and WAN at major datacenters and campuses. Enterprise switches and routers deployed in these environments offered span ports, and thus a generation of NPM packet capture (PCAP) appliances were born that could attach to these span ports directly or via a convenient tap or packet broker device. Appliances weren't the exclusive domain of NPM offerings – they were used for many network management and security products and still are – but the majority of packet-centric NPM solutions leverage appliances to achieve scale and PCAP storage objectives.

A funny thing happened though – the cloud. The rise of IaaS, PaaS, and SaaS meant that there was a new breed of alternative for just about every IT infrastructure and application component. Applications becoming more and more distributed and, increasingly, components started living not just in separate containers, VMs and infrastructure clusters, but in separate datacenters, spread out across networks and the Internet. This cloud way of developing, distributing, hosting and communicating established a dramatically altered set of network traffic patterns.

Unfortunately, NPM appliances aren't nearly as helpful in this new reality. In many clouds you don't have a network interface to tap into for sniffing or capturing packets. The proliferation of application components multiplies the communication endpoints.

In addition, digital business means that users aren't necessarily reached across a private WAN, but rather across the Internet.

Finally, appliances are bedeviled by limited storage and compute power, so they can't offer very much depth of analysis without extreme cost impact. With digital business and DevOps practices being so data-driven, being limited to summary reports and a small window of details isn't acceptable anymore, especially when scale-out computing and storage is so readily available.

This change in how the network and Internet interacts with and influences application performance requires a new approach to NPM. NPM for the digital operations era needs to offer a level of flexibility in deployment and cost-effectiveness to allow for broad, comprehensive instrumentation to collect network performance metric data. In addition, the volume of network performance data ingest, depth of storage, and analytical sophistication needs to scale based on today's cloud economics. Fortunately, there are plenty of technology options available to build these capabilities. So while Gartner has rightly identified a gap in NPM, the good news is that the gap can be readily filled.

Jim Frey is VP of Strategic Alliances at Kentik
Share this

The Latest

February 14, 2019

Part 3 of our three-part blog series on the shortcomings of traditional APM solutions for monitoring microservices based applications explains how the alerting and troubleshooting capabilities of traditional APM do not address the evolving requirements of monitoring microservices based applications ...

February 13, 2019

In a digital world where the speed of innovation matters, are you anchored down by legacy APM agents? ...

February 12, 2019

In a digital world where customer experience defines your business, is your APM solution doing its job? This may seem like a strange question to open a technical blog on Application Performance Management (APM), but it's not. With customer experience today largely driven by software, we think there's no more important question to ask ...

February 11, 2019

According to the NetEnrich 2019 Cloud Adoption survey, 68% of enterprise IT departments are using public cloud infrastructure today, and 27% of respondents said that doing so is part of their near-term plan ...

February 08, 2019

Organizations and their IT teams are not in sync when pursuing their digital transformation strategies, according to a new report released today by The Economist Intelligence Unit ...

February 07, 2019

Having the right tools and good visibility are critical to understanding what's going on in your network and applications. However, as networks become more complex and hybrid in nature, organizations can no longer afford to be reactive and rely only on portable diagnostic tools. They need real-time, comprehensive visibility ...

February 06, 2019

When building out new services, SaaS providers need to keep in mind a set of best practices and "habits of success," which cover their organization's culture, relationships with third-party providers and customers, and overall strategic decisions and operational know-how. If you're a SaaS application provider, here are five considerations you need to keep in mind ...

February 05, 2019

In the coming weeks, EMA will be gathering data on what we believe is a unique research topic — approaching DevOps initiatives from the perspectives of all key constituents. We're doing this to try to break through some of the "false walls" created by more niche, market-defined insights, or some of our industry hyperbole. Here are some of the directions we're pursuing ...

February 01, 2019

An application on your network is running slow. Before you even understand what the problem is, the network is blamed for the issue. This puts network teams in a dangerous position — guilty until proven innocent. Even when network teams are sure an issue doesn't stem from a network problem, they are still forced to prove it, spending sometimes significant amounts of time going through troubleshooting processes, looking for a problem that doesn't exist ...

January 31, 2019

Tap and SPAN. It's the same thing, right? That answer would be wrong. Some network engineers may not know the difference, but there are definitely clear and distinct differences between these two types of devices. Understanding these differences will help you elevate your game when it comes to network performance monitoring and application performance monitoring ...