Contents | Previous | Next

Alert Events - Logging to a File

The "Log to file" event writes data to a text file whenever alert conditions are met.

With the "log to a file" event you have an added option specific to this event called "Log times for entire route?".
This option specifies if you want to write data to the text file just for the monitored host, or the entire route. Leaving this off means that for each time alert conditions are met, one data item will be written to the file – for the monitored host. If this switch is turned on, then data for the entire route will be written.

The Filename box.
The filename is *required* to have the $host variable in it. If it's missing, then the file will be nonsensical if you attach this alert to more than one host. The following variables (below in blue) can be used as part of the filename. Note there is no way to "escape" the following sequences, so these are always parsed and can't be specified as literals in the filename.

$host The monitored host – i.e.: the target that failed.
$dest The destination for PingPlotter. This may or may not be the same as $host – it will match if you're monitoring the final destination, but won't match for intermediate hops.
$year Current 4 digit year (i.e.: 2003)
$month Current 2 digit month (i.e.: 03)
$day Current 2 digit day (i.e.: 08)
$date Date, 4-2-2 format (i.e.: 2003-03-08) for March 8th.
$hour 24 hour format, (i.e.: 06)
$minute 2 digit minute, (i.e.: 02)

Note that one directory level of depth will be created automatically, if it doesn't already exist, so you can specify c:\ppdata\$host\filename.txt, and the $host directory will be created as needed. Only one directory of depth will be created, however, so if the c:\ppdata directory didn't already exist, an error will occur.