...
After creating job commands ,submit it via machine noric or yakut (pinger is not licensed for running batch jobs) using the command line interface. See wrapper_for_daily or wrapper_for_hourly.pl help for more options.
Analyze-allmonths.pl and analyze-allyears.pl
analyze-allmonths.pl uses the daily aggregated data, e.g.
| Code Block |
|---|
> zmore /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-100-by-site-1998-01.txt.gz
Jan01 Jan02 Jan03 Jan04 Jan05 Jan06 Jan07 Jan08 Jan09 Jan10 Jan11 Jan12 Jan13 Jan14 Jan15 Jan16 Jan17 Jan18 Jan19 Jan20 Jan21 Jan22 Jan23 Jan24 Jan25 Jan26 Jan27 Jan28 Jan29 Jan
30 Jan31
sgiserv.rmki.kfki.hu www.cern.ch . . 26.000 25.000 25.000 26.000 26.000 25.000 25.000 26.000 25.000 26.000 24.000 24.000 24.000 24.000 . . . . . . . 25.000 25.000 26.000 25.000
26.000 26.000 26.000 25.000 sgiserv.rmki.kfki.hu www.cern.ch
...
|
So once we have the daily we do not have to go back and reanalyze data for each year, since trscrontab runs analyze-allmonths.pl each month
analyze-allyears.pl uses the allmonths aggregated data, and runs on demand or once yearly from trscrontab, so as long as analyze-allmonths.pl has run analyze-allyears is fine.
So "all" that is needed is to modify analyze-allmonths.pl and analyze-allyears.pl to aggregate the extra metrics and then run them