For PingTime to record the response times, we need to establish some tasks to run on a regular basis (via Cron or At).
This task will run every xxx seconds, where xxx is the collection interval.
If you want 5 minute samples, then this command file should be set to run every five minutes.
The command file is a simple text file that lives in /var/opt/OverTime/cfgs/ in Unix or /OverTime/cfgs on NT/2000.
The command file’s name has a user definable prefix specified, as pt_cmds, in the overtime.cfg file (from $OV_BIN).
The default value for the parameter “pt_cmds” is “PingTime-“ which means that the command file that will be run would
be /opt/OverTime/cfgs/PingTime-300 for a 5 minute collection in Unix and /OverTime/cfgs/PingTime-300.bat on NT/2000.
The “300” indicates this command file will be run every 300 seconds (as a convenient reminder).
When the first PingTime entry is created this file will be created, otherwise it is simply updated.
If you have set a different “sample_time” in overtime.cfg, then all new PingTimes will be created with this interval.
You need to ensure that a suitable Cron/At also runs at this interval and runs the appropriately named PingTime-xxx.
This is the once only configuration that you need to perform.
A Unix "cron" entry such as :
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /var/opt/OverTime/cfgs/PingTime-300 > /var/opt/OverTime/logs/PingTime-300.log
would run the collections every 5 minutes and also keep a simple log.
An "at" command such as:
at 23:55 /every:m,t,w,th,f,s,su \OverTime\bin\batch.bat
might be the 11:55pm instance that was set in place by "schedule.bat" that comes with PingTime for NT/2000.