Introduction
This page describes, how the data collected by the SLAC PingER site, ends up as information, which is used by pingtable, motion charts, intensity maps and several other applications.
Scripts
- TimePing:
- /afs/slac/package/pinger/timeping.pl
- Represents the old script to perform ping measurements and store raw data.
- Stores raw data on nfs at:
/nfs/slac/g/net/pinger/pinger_mon_data/ping-<YYYY>-<MMM>.txt
- PingER2:
- /afs/slac/package/pinger/pinger2/share/pinger/pinger2.pl
- Represents the new Tool to perform ping measurements and store raw data.
[http://confluence.slac.stanford.edu/display/IEPM/PingER2+at+SLAC]
- Stores raw data on nfs at:
/nfs/slac/g/net/pinger/pinger2/data/ping-<YYYY>-<MMM>.txt
- Ping_Data
- /afs/slac/g/www/cgi-wrap-bin/net/offsite_mon/ping_data/ping_data.pl
- Represents the web interface(cgi script) used to fetch data from remote monitoring node.
- zips the data before transfer.
- GetData
- /afs/slac/package/pinger/getdata.pl
queries ping_data[http://slac.stanford.edu/cgi-wrap/ping_data.pl] to fetch data.
- Stores zipped File at
/nfs/slac/g/net/pinger/pingerdata/hep/data/<host>/ping-<YYYY>-<MMM>.txt.gz
- See Restoring PingER data for more details.
- Analyze
- group of analysis scripts, that pick up zipped data; do their analysis, aggregate data and prepare web reports..
- store the reports at
/nfs/slac/g/net/pinger/pingerreports/hep/<metric>-<size>-by-<site|node>(-<YYYY>?)(-<mm>?)(-<dd>?).txt.gz
- PRM
- /afs/slac/package/pinger/prm/prm.pl
- The script prm.pl, is used to create csv files for the analyzed data which can then be used by PingER motion charts or PingER Executive Plots.
- The script requires a configuration file, which contains entries for all the reports prm should create. These entries are of the form:
<metric name> <monitoring site> <country||continent> <tick> (<filter>?)
- The reports created by prm are available online.