nanog mailing list archives
Re: Analysing traces for performance bottlenecks
From: Sean Donelan <sean () donelan com>
Date: Thu, 17 Jul 2008 12:40:12 -0400 (EDT)
On Thu, 17 Jul 2008, Sam Stickland wrote:
Something that could provide a similar, automated analysis of a TCP stream capture is what I'm after, although I doubt a standard packet capture will be able to provided as many metric as web100 stack can.
There are several similar tools designed for ISP customer care centers to help analyze network problems reported by customers. Customer calls with complaint, agent clicks on tool and asks customer to try what isbroken, tool analyzes traffic and guesses what's wrong. CC agent then reads from the script for fixing problem X.
They tend to be expensive and are designed for point-click call center agents. The back-end analysis some of these systems attempt is impressive, even if the output is overly simplistic. The one I'm most familar with was Adlex <http://www.adlex.com/> which has been purchased by CompuWare. But there are several others.
Current thread:
- Analysing traces for performance bottlenecks Sam Stickland (Jul 15)
- Re: Analysing traces for performance bottlenecks Tim Eberhard (Jul 15)
- Re: Analysing traces for performance bottlenecks Sam Stickland (Jul 15)
- Re: Analysing traces for performance bottlenecks Kevin Oberman (Jul 15)
- Re: Analysing traces for performance bottlenecks Matt Cable (Jul 15)
- Re: Analysing traces for performance bottlenecks Sam Stickland (Jul 17)
- RE: Analysing traces for performance bottlenecks Bulger, Tim (Jul 17)
- RE: Analyzing traces for performance bottlenecks Tim Sanderson (Jul 17)
- Re: Analyzing traces for performance bottlenecks Randy Bush (Jul 17)
- Re: Analysing traces for performance bottlenecks Matt Cable (Jul 15)
- Re: Analysing traces for performance bottlenecks Sean Donelan (Jul 17)
- <Possible follow-ups>
- Re: Analysing traces for performance bottlenecks rcheung (Jul 15)