• Created by Unknown User (jaredg), last modified on Mar 18, 2008

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

How does PingER collect data?

  1. The monitoring host collects data on its local disk
    • The data for most PingER v2 sites is stored in /usr/local/share/pinger/data
    • For the SLAC monitoring host, the data is stored in NFS at /nfs/slac/g/net/pinger/pinger_mon_data. This is the "raw" data just showing the ping times from SLAC to the rest of the world. It is retrieved the same way as any other monitoring host, via http://www.slac.stanford.edu/cgi-wrap/ping_data.pl .
  2. A trscron job run as the pinger user on the pinger host runs getdata.pl which contacts a web server at each monitoring site and requests that site's data with the ping_data.pl script.
    • This data is stored on NFS in /nfs/slac/g/net/pinger/pingerdata/hep/data/<hostname>
  3. A trscron job run as the pinger user on the pinger host runs checkdata_gif.pl which validates that the data has been collected and sends the email reporting on missing data. This is scheduled for ~ 2 hours after getdata.pl is run. checkdata_gif.pl uses checkdata.pl which looks at each of the data files for the month in the NFS path mentioned above.
  4. LSF batch jobs are submitted for the analyze_* scripts. Each script is run four times, for 100 and 1000 byte pings and for by-site and by-node aggregation. A report is created for each metric, e.g. packet loss, average RTT, estimated theoretical throughput, etc. These files are created in /nfs/slac/g/net/pinger/pingerreports/<metric name> and are named like: <metric name><packet size><by site/node>-<time period>.txt.gz
    1. analyze-hourly.pl runs first. It takes the data gathered from the monitoring sites in /nfs/slac/g/net/pinger/pingerdata/hep/data and creates a report for a whole day with one data point for each hour.
    2. The remaining scripts all depend on the results of analyze-hourly and can be run anytime after it has completed.
      1. analyze-daily.pl by default creates a report covering a whole month with one data point for each day.
      2. analyze-daily.pl with the --date 60days option creates a report covering the last 60 days with a data point for each day.
      3. analyze-daily.pl with the --date 120days option creates a report covering the last 120 days with a data point for each day.
      4. analyze-monthly.pl creates a report covering the last 24 months with one data point for each month.
      5. analyze-allmonths.pl creates a report covering all months for which there is data with one data point ### analyze-for each month.
  • No labels