Versions Compared

Old Version 32

changes.mady.by.user Unknown User (shahryar2001)

Saved on

compared with

New Version 33

changes.mady.by.user Unknown User (shahryar2001)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Modules

Function

SelectConvSrcDest1.pm

This program is to be setup as a cron job to run every 24 hours (after installing on a server with a PingER data source)
This script is to be run once the data for all sources have been brought to the server from various monitoring sites using getdata.pl.
This program finds unique SourceSite_DestinationSite_PacketsSize_NumberOfPings(maximum) combinations and creates a srcdest.txt file agaist each combination.
It calls the PingERtoSmokeping application to convert the data agaist each of the unique SourceSite_DestinationSite_PacketsSize_NumberOfPings(maximum) combinations found.

PingERtoSmokeping.pm

PingERtoSmokeping.pm is a tool to convert PingER data files into Smokeping data files.
The output of this program is an rrd file for a SourceSite_DestinationSite_PacketsSize_NumberOfPing combination present in a PingER data file.
This tool does not take any arguments from command line.

Configuration files

                                                                                                          Function

srcdest.txt

The file that stores unique SourceSite_DestinationSite_PacketsSize_NumberOfPings(maximum) combinations found in PingER data.

CGIs

Function

form.cgi

Displays the  SourceSite_DestinationSite_PacketsSize_NumberOfPings(maximum) RRDs(data) available for the monitoring site or node slected from pingtable.pl by user.

graph.cgi

Generates graphs from the rrd files on the fly and display them to the user and then deletes the graph from cache

saveimage.cgi

Displays the contents of the image to the user

...

Code Block
CreateRRD took:22 wallclock secs (19.75 usr  0.79 sys \+  2.60 cusr  0.75 csys = 23.89 CPU)
CreateRRD took:21 wallclock secs (19.66 usr  0.85 sys \+  2.70 cusr  0.76 csys = 23.97 CPU)
CreateRRD took:24 wallclock secs (20.49 usr  1.44 sys \+  2.49 cusr  0.83 csys = 25.25 CPU)
CreateRRD took:23 wallclock secs (20.77 usr  1.11 sys \+  2.53 cusr  0.88 csys = 25.29 CPU)
CreateRRD took:23 wallclock secs (20.88 usr  1.26 sys \+  2.40 cusr  0.90 csys = 25.44 CPU)
CreateRRD took:24 wallclock secs (20.91 usr  1.06 sys \+  2.39 cusr  0.96 csys = 25.32 CPU)
CreateRRD took:21 wallclock secs (19.11 usr  0.50 sys \+  2.42 cusr  0.97 csys = 23.00 CPU)
CreateRRD took:21 wallclock secs (19.13 usr  0.62 sys \+  2.58 cusr  1.02 csys = 23.35 CPU)
CreateRRD took:23 wallclock secs (20.77 usr  1.12 sys \+  2.56 cusr  0.82 csys = 25.27 CPU)
CreateRRD took:23 wallclock secs (20.79 usr  1.12 sys \+  2.36 cusr  0.87 csys = 25.14 CPU) 

 While data for NCP monitoring site took very minimal time because it monitors few links. SLAC monitoring host took an average of 500 seconds for the creation of each RRD. Here is the data for the creation of 3 RRDs

Code Block

 CreateRRD took:511 wallclock secs (419.57 usr 22.94 sys + 51.11 cusr  6.53 csys = 500.15 CPU)     CreateRRD took:503 wallclock secs (416.39 usr 21.93 sys + 50.49 cusr  4.99 csys = 493.80 CPU)     CreateRRD took:504 wallclock secs (416.66 usr 22.82 sys + 50.44 cusr  6.41 csys = 496.33 CPU) 

 The update function takes very little time even for SLAC monitoring host. Here is the data for the update function for the same three RRDs

...