7 Replies Latest reply on Sep 14, 2009 6:05 PM by Donald_Francis

    Too basic to be a good troubleshooting tool?


      Because of cost, we recently moved from the Fluke(Crannog) Netflow Tracker product to the Solarwinds Netflow Traffic Analyzer. Perhaps it's just the "learning a new product" blues but so far, I feel like I've replaced my dashboard gauges with idiot lights.

      When I choose a device in Netflow Tracker, I get a chart of all the reporting interfaces showing inbound and outbound utilization. Select an interface and I get a differentiated bar chart of all inbound and outbound traffic. I select a timeframe, right click and I get about a bazillion options to filter the selected data. I can view inbound, outbound or all traffic. I can view it by source, destination, conversation or any of dozens of other viewpoints. Once I've selected and viewed my filtered data, I can filter THAT again to further isolate whatever traffic I'm looking for, if necessary.

      With Netflow Traffic Analyzer, I get to filter by endpoint or application. Fine. So I type in the address of my workstation and click on search. What do I get? I get the list of all interfaces and I get to open each interface one at a time (twiddle thumbs while waiting for the view to build) to see if there was traffic? Once I get all my routers in Netflow that would be an all day project. No thanks.

      With Netflow Tracker, I get to see ALL the selected data. The top ten are specifically charted and the rest are lumped into a group called "Others". This way, if I selected inbound or outbound traffic, I get to see TOTAL bandwidth used and how much my top talkers are using individually.

      With Netflow Traffic Analyzer, I get the Top XX conversations, or Top XX whatevers. I even have to figure out myself if it's inbound or outbound traffic so my Top displayed talker(s) may not even be involved if I'm having an inbound problem and the top talkers are outbound. I also don't know percentage of bandwidth utilized since both inbound and outbound traffic are reported in this Top XX approach.

      I even thought I'd be sneaky so I put an interface bandwidth utilization chart at the top of my Netflow Interface Details View so I'd at least be able to have utilization data in the same view I was using but all I got was a little square with an X in it...not very helpful.

      As a last resort I even checked the manual.....no help. I looked for tutorials, none exist.

      So....I really have to wonder...am I missing something? Maybe someone has created a bunch of reports to alleviate all the issues I'm having? I'd sure appreciate some feedback.


                    Dan Goodale - Network Engineer

                    Triwest Healthcare

        • Re: Too basic to be a good troubleshooting tool?


          Thanks for the post.  We really appreciate the frank and honest feedback.  We're working on a number of enhancements that would be helpful in addressing some of the use-cases you described (see this post: OLD - what we're working on).  

          I'd like to setup a gotomeeting with you to run through the following:

          1) Use-cases you described above using NTA today.   There may some things that we can do now that you may not be aware of.  If not, I'd like to make sure I'm capturing your use-cases correctly.

          2) Demo of the things we're working on and get your feedback.  We've got some really cool things coming to make our visualization of data more valuable.

          You should be receiving a private email from me shortly.

          I'd like to also extend the invite all others who feel the same way as Dan (and would like a preview demo of what we're working on) to send me an email through Thwack.