- BlackBerry Storm vs. the iPhone
- Digg's Kevin Rose: "We have to do better"
- Blogger warns: "Nortel doesn't make it out alive"
- Financial quagmire bringing out the scammers
- Verizon plays with the wrong e-mail addresses
Newsletters | Podcasts | Chats | Opinions | RSS Feeds | This Week In Print | IT Careers | Community | Reports | Downloads | Slideshows | New Data Center
Partner Sites:Application Performance Solutions | App Performance | Networking Solution | SafeGuard Enterprise Solution Center | SOA | Test your Web Filter | Value of WDS
WAN experts Steve Taylor and Jim Metzler analyze and share best practices on WAN issues from optimization to management.
In a series of recent newsletters (see the list at the end of this newsletter), we’ve discussed the fact that the Mean Time to Repair (MTTR) application performance issues can be quite lengthy and we described some of the reasons why.
Given the number of responses that we’ve received, it is clear that we struck a cord with a number of readers. One reader responded that the newsletters were relevant to her because her organization had just spent an entire frustrating week troubleshooting one enterprise application. She noted that the root cause of the problem was never isolated but that a reboot of the three relevant Web servers ultimately resolved the problem.
While she was glad that her organization eventually resolved the problem, she expressed understandable concern about the process that took place. The way she described it, the application and server teams insisted the problem was the network, and of course her organization had to prove the network was not the issue before those organizations would consider looking at their components. As we pointed out previously, the amount of time that the network organization has to spend proving that the network is not at fault before the rest of IT gets involved in troubleshooting is one of the factors that lengthen the MTTR application performance issues.
Our reader went on to say that they were running NetQoS’s SuperAgent and Reporter Analyzer, as well as NetVoyant, and that these tools showed that nothing on the network was outside of its normal long term baselines. They also had vendors such as AT&T confirming that they had an error-free environment. In spite of all of that, they still had a very difficult time convincing the other teams that the network was not at fault, even when SuperAgent clearly pointed to the application server tier as the source of the problem.
She concluded by saying that it makes her feel sad and defeated to think that the investment and effort that her organization has made in deploying monitoring tools was being devalued because not one person outside of the network team believes in and takes much consideration of the data. She ended on an optimistic note: “Momentum is slowly moving in our direction and this amazes me as our tools, visibility and transparency are light years beyond what any other group is doing.”
Steve Taylor is president of Distributed Networking Associates and publisher/editor-in-chief of Webtorials. Jim Metzler is vice president of Ashton, Metzler & Associates.
Partner Content
Simplify Your Branch Infrastructure
Learn how to simplify your branch infrastructure while dramatically increasing app performance with Citrix Branch Repeater.
Download the Free Info Kit
Next-Gen Load Balancing
Free Guide: "Next Gen Load Balancing: 8 Things You Need to Handle Today's Network Traffic" shows you the functionality needed in your next load balancer.
Download the Free Guide
Accelerate Your Web Apps by up to 5x
Free Guide: "The Secret to Getting Maximum Speed from your Web Applications." Learn how you can deliver Web apps up to 5x faster.
Download the Free Guide
Comments (4)
Biggest lie in the enterprise: `The network is down'By Julie Bort on July 12, 2007, 1:09 pmThe network is rarely down. So why do network folks constantly take the rap? One reader wrote a thoughtful essay on this -- and what network folks need to do to...
Reply | Read entire comment
Why are we reinventing the wheel?By Fitz on July 5, 2007, 10:19 amAs a retired Network Geek I don't know how many times I've seen this very same problem over the twenty odd years I've trouble shoot networks. In the Mainframe era...
Reply | Read entire comment
Great topic. One of theBy Ben Haley on June 26, 2007, 10:05 amGreat topic. One of the issues I see is a desire for monitoring to show the end user experience is or the business transaction. That approach is great at identifying...
Reply | Read entire comment
Don't blame the network for application problemsBy Anonymous on June 26, 2007, 9:15 amSteve, Every time I come across an article of interest, it is co-written by you. Re: Don't assume application performance problems are always network-related. Your...
Reply | Read entire comment
View all comments