Versions Compared

Key

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

...

  PingER SmokePing Integration aims at using Smokepings's rrd tool to visually display pingER's data  in the form of graphs.

Note

This requires more in-depth description of why this project is interesting and what benefits this offers over not doing it, and what it offers over the current suite.

Background

Note

Need some background as to what the format of the pinger files are, and where they are located

RRD Format

Note

you need to mention that the the pinger data is to be converted into rrds. this section needs to determing the mapping between the pinger logs and the rrd data form. indepth description of the rrd creation and data structure needs to be mentioned here. also what are the benefits and disadvantages of the rrd structure.

Package Description

Note

it is difficult to relate to any of this information because you don't ahve any background on what the things are.

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

Detailed description can be found at http://maggie.niit.edu.pk/newwebsite/federation_projectdesc2.html

Installation

/newwebsite/federation_projectdesc2.html

Installation

Note

perhaps you should develop an automated installation script rather than document all of this.

SelectConvSrcDest1.pm

  • Modify the following path to point to the bin directory containing the PingERtoSmokeping.pm
    Code Block
    use lib qw(/home/bin);
    
  • Change following paths according to local system. Point this path to the pinger data files directory
    Code Block
    my $some_dir="/home/pinger/pingerdata/hep/data";
    
  • Point this path to the directory SRCDEST_FILE
    Code Block
    my $srcdest="/home/SRCDEST_FILE";
    

...

Code Block
use lib "/afs/slac.stanford.edu/package/netmon/rrdtool/lib/perl/5.8.8";
use lib "/afs/slac.stanford.edu/package/netmon/rrdtool/lib/perl/5.8.8/i386_linux24";
.stanford.edu/package/netmon/rrdtool/lib/perl/5.8.8/i386_linux24";
Note

the above library paths should not be used, there is a sitewide distribution of rrdtool under /package/rrdtool. if this does not work, then you should work with sysadmin to get it to work.

The problem I faced with this is that it was unable to link the dynamic library (.so) file at the run time which I ran it from Flora but when I ran it from 

Note

flora is a sun machine. i don't believe the rrd stuff is deployed on it.

PingER it worked fine. The problem was due to the fact that Flora is a 64 bit machine.

...