For PingTime to record the response times, we need to establish some tasks to run on a regular basis (via the AT command).
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 /OverTime/cfgs.
The command file’s name has a user definable prefix specified, as pt_cmds, in the overtime.cfg file.
The default value for the parameter “pt_cmds” is “PingTime-“ which means that the command file that will be run would
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 AT job also runs at this interval and runs the appropriately named PingTime-xxx.
This is the once only configuration that you need to perform.
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.