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

Compare with Current View Page History

« Previous Version 22 Next »

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. Various scripts are used in turn to generate the data. The scripts in their turn are driven by a trscrontab that executes on pinger@pinger.slac.stanford.edu.

Scripts

IMPROTANT:    /nfs/slac/g/net/pinger/pingerreports/hep/<metric> contains the  recent years data however /nfs/slac/g/net/pinger/pingerdata/hep/data contains old data(from 1998 to 2007) for nodes.

  • 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>?)
    • It gets its data from pingtable.pl either by calling it locally or by accessing it via the web.
    • The reports created by prm are available online.
    • The reports are used by the metric motion plots, the metric maps and the executive plots.

Anomalies

We have spotted anomalies between the values reported by:

  • table.pl and pingtable.pl
  • and pingtable.pl at SLAC and pingtable.pl at SEECS

They are discussed and explained in the Anomalies report.

  • No labels