[rrd-users] Re: [mrtg] VISIONARY: New tool to consider to create: a "Dynamic Data Set" tool...

Bradford Woodcock bwoodcoc at Genuity.com
Wed Nov 22 15:41:33 MET 2000

Hi Jakob,

I am looking to do a pilot along these lines now. We use Netscout probes at
many points within our network. I want to produce Top Conversation reports
for any interval with high utilization. Here is what I know so far.

- A script to be written will be executed upon an mrtg threshold. In fact
we already have a script to log each interval and also display current
performance issues to a web status page (utilization, errors, congestion,
etc.). This script will be extended or spawn another to handle top talkers.
- The only problem with this technique is that what will be reported is the
top talkers for a 30 second interval AFTER the 5 minute mrtg threshold was
hit. So it is a bit out of sync but I believe it will still allow us to
capture the power users consuming bandwidth on our wan.
- I need a technique to relate target name to a Netscout agent name. This
will hopefully be dynamic and stored into the config of the probe and
extracted periodically by another script....but I'm not sure yet.
- The script will execute a Netscout cli command (dvsnap) to request from
the agent the TopN Conversations (source and destination) and store the
data probably in a csv file with the name relating to the mrtg target name
and a time stamp (ex. targetName.20001122.09.25).
- An interface (or button) will be added to our main status web page to
review TopTalkers for a given target....somehow.

I do not have a vision of producing a graph. The data will be csv and would
be converted to html table format upon viewing. We have everything under
the sun in this format (can you say datawarehouse without the house?) and
this will work perfectly well, this I already know. Note that the
collection of ALL conversations as a report is not the goal, only those
during peak utilization and also only TopN. Additionally only wan links
will be targeted (where the money is spent) but I hope to add one-off
targets for adhoc usage for performance analysis for lans when needed. I
believe this strategy will scale and we will prevail with this data before
the end of the year if Netscout lives up to my expectations. The only
aspect I actually have done so far is a quick test with Netscout's cli
dvsnap command which seems to fit the need. So I have quite a bit of work
ahead of me but it will be well worth it provided I'm successful.


Unsubscribe mailto:rrd-users-request at list.ee.ethz.ch?subject=unsubscribe
Help        mailto:rrd-users-request at list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/rrd-users
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi

More information about the rrd-users mailing list