11:26 AM
Jim Rapoza
Jim Rapoza
Connect Directly
Repost This

There's No 'I' in Team--Or App and Network Performance Management

Much like in football, successful application and network performance requires all teams to work together. Learn why you should abandon the siloed approach to infrastructure and start working with the other teams.

Football season is in full swing, and, like many fans, I'm eagerly consuming news items, reports and replays of the top games of the week. And when you watch a lot of football programming, you regularly see coaches and experts talking about the elements and practices that separate the top teams from the bottom dwellers.

A common refrain that coaches and experts repeat is the importance of all three phases of the game and how all the units of the team need to work together to succeed. Watching games, it's easy to see that in action: Teams with good offenses but lousy special teams and defense can put up a lot of points but often don't make it to the postseason or don't last long if they do.

But this is a lesson that, for a while, hasn't taken hold in the application and network performance infrastructures of many businesses. In fact, it has been all too common for a company to have an application team that worries just about testing and has little concern for network issues. Or network admins who are looking at only network capacity and not at how performance affects the user experience.

Clearly, these organizations need a good head coach who can whip them into shape and ensure that all groups are working together to achieve the highest levels of application performance. That's because many of these same team-oriented principles apply just as much, if not more, in application performance management as they do in football.

When an application suffers from a performance or usability issue, the cause could be in the code, or due to a server or network issue, an interface design flaw, or some combination of the above. The code flaw could be found by testing tools used by the development team, but they would be ignorant of the server issues that would be readily apparent to the data center team.

The first step to overcoming this problem is to get the different teams to stop their siloed approaches and start working together. But this solves only part of the problem.

The other issue is that the different teams don't really understand or know how to get the most value out of the performance management and monitoring tools in use by each group. Testing and debugging tools can be as hard for network admins and business managers to understand as a quarterback's playbook would be to a defensive tackle.

And while business managers might understand that red lights are bad in a network monitoring console, they won't really know how to figure out what the underlying issue causing the red lights is. That's why the next step is to improve translation layers and integration among the different performance management tools in use by each group. By enhancing the flow of information, this can make it possible for the different teams to work together to understand application performance and detect and remove potential issues.

And these steps can pay off in improved application performance and increased monitoring and management capabilities. In my recent report, Overcoming Application Performance Walls, survey data showed that businesses that have a unified approach to performance management are 75% more likely to have implemented capabilities such as identifying sources of delay in application performance. And this approach should become more common in businesses, as 88% of organizations centralize management of application performance, or plan to in the next 12 months.

In football, when the offense fumbles the ball, it isn't just their problem. The defense has to go out and limit the damage of the turnover, and special teams needs to ensure good field position to get the offense back on track.

Similarly, when an application fails, it isn't just the application development team's problem. When all of the groups within an IT infrastructure are able to work together to manage performance, everyone wins.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
User Rank: Apprentice
12/6/2012 | 9:03:54 PM
re: There's No 'I' in Team--Or App and Network Performance Management
So jeolous of the football analogy...well played...well played...88% of the enterprises should be asking their MPLS providers for an application aware network monitoring tool that is easy to use and provides real time and back in time analysis which is time syncronized for the network, application, CoS, and VoIP data...easy to use and available from their service providers...for an monthly recurruing charge (operations) why go buy a system...?
User Rank: Apprentice
10/2/2012 | 4:20:59 PM
re: There's No 'I' in Team--Or App and Network Performance Management
Jim suggests that G«ˇ88% of organizations centralize management of application performance, or plan to in the next 12 months.G«÷

This is interesting. The article suggests that application and network management are becoming increasingly important to businesses, along with the realisation that an efficient network impacts the whole companyG«÷s IT infrastructure.

This piece suggests that creating a cohesive IT team which oversees all aspects of application/network management will be the aim for many businesses in the near future. I wonder whether this will be trickier to navigate for the larger companies, whose network infrastructures will be highly complex. Will they in turn look to bring in external help to streamline their teams, as well as their networks? But overall a good article, and an interesting approach to a complicated topic.

User Rank: Apprentice
9/28/2012 | 5:25:29 PM
re: There's No 'I' in Team--Or App and Network Performance Management
Thanks Tom. I tried to figure out a way to work a replacement ref concept in but it wasn't working.
User Rank: Apprentice
9/26/2012 | 6:32:04 PM
re: There's No 'I' in Team--Or App and Network Performance Management
keep up the good work Jim. I think the football analogy is spot on.

Overall, I think this piece gives credence to a transaction-centric vision of APM. One that is holistic and monitors end to end. BCI tools are great for diagnosing problems in Java and .NET based application, but cannot give as much performance data on other application components or programming languages. However, the fact still remains that IT teams need a customizable for solution for their specific organization's needs:

This could even mean instances where large IT teams use BCI in conjunction with a more Ops centric tool.
More Blogs from Commentary
SDN: Waiting For The Trickle-Down Effect
Like server virtualization and 10 Gigabit Ethernet, SDN will eventually become a technology that small and midsized enterprises can use. But it's going to require some new packaging.
IT Certification Exam Success In 4 Steps
There are no shortcuts to obtaining passing scores, but focusing on key fundamentals of proper study and preparation will help you master the art of certification.
VMware's VSAN Benchmarks: Under The Hood
VMware touted flashy numbers in recently published performance benchmarks, but a closer examination of its VSAN testing shows why customers shouldn't expect the same results with their real-world applications.
Building an Information Security Policy Part 4: Addresses and Identifiers
Proper traffic identification through techniques such as IP addressing and VLANs are the foundation of a secure network.
SDN Strategies Part 4: Big Switch, Avaya, IBM,VMware
This series on SDN products concludes with a look at Big Switch's updated SDN strategy, VMware NSX, IBM's hybrid approach, and Avaya's focus on virtual network services.
Hot Topics
Converged Infrastructure: 3 Considerations
Bill Kleyman, National Director of Strategy & Innovation, MTM Technologies,  4/16/2014
Heartbleed's Network Effect
Kelly Jackson Higgins, Senior Editor, Dark Reading,  4/16/2014
White Papers
Register for Network Computing Newsletters
Current Issue
Twitter Feed