You can now track changes on critical system and user files and be notified if a specific change occurs.
E.g. If you want to get notified about an increase in a file's size, you can configure an appropriate file monitoring template with a file size monitor and apply the same to devices in which you want the files monitored.
Using file monitoring, you can monitor the following parameters on Windows/ WMI based devices:
Configure the monitoring criteria based on which you want to be notified:
Click here to know more on this type of monitor and the prerequisites to be satisfied for log file monitoring.
You can customise your alarm message generated when a provided criteria is violated, by using these alarm variables in the Alarm Message Format field:
Note: The variable $CURRENTVALUE works differently for File Contains and File Age/Size. For File Contains criteria type the provided search string is returned, whereas it returns the latest polled value for File Age/File Size criteria types.
|Criteria type||Supported alarm variables||Sample alarm message with variables||Generated alarm message|
|File contains||$MONITOR - Monitor name
$CURRENTVALUE - Search string
|File monitor $MONITOR contains the string $CURRENTVALUE||File monitor FileMonitor1 contains the string test|
|File Existence||$MONITOR - Monitor name||
File monitor $MONITOR exists
File monitor $MONITOR does not exist any more
File monitor FileMonitor2 exists
File monitor FileMonitor2 does not exist any more
|File Size||$MONITOR - Monitor name
$THRESHOLDVALUE - Minimum size of file required to trigger the alarm (in bytes/KB/MB/GB)
$CURRENTVALUE - Current size of the file in the path (in bytes/KB/MB/GB)
$UNITS - Units provided for the threshold value (bytes/KB/MB/GB)
|File size of the monitor $MONITOR is $CURRENTVALUE, violating the threshold of $THRESHOLDVALUE $UNITS||File size of the monitor FileMonitor3 is 2, violating the threshold of 1 GB|
|File Age||$MONITOR - Monitor name
$THRESHOLDVALUE - Minimum size of file required to trigger the alarm (in seconds/minutes/hours)
$CURRENTVALUE - Current size of the file in the path (in seconds/minutes/hours)
$UNITS -Units provided for the threshold value (seconds/minutes/hours)
|File age of the monitor $MONITOR is $CURRENTVALUE, violating the threshold of $THRESHOLDVALUE $UNITS||File age of the monitor FileMonitor4 is 95, violating the threshold of 90 mins|
|File Modification||$MONITOR - Monitor name
$MODIFIEDTIME - Latest value for Modified Time of the value (MM/DD/YYYY HH:MM:SS AM/PM)
|File monitor $MONITOR got modified at $MODIFIEDTIME||File monitor FileMonitor5 got modified at 8/13/2017 1:12:35 AM|
Having created a template with the alert criteria, you can now associate the template to the devices.
The monitor is now added to the device and OpManager raises alerts based on the alert conditions provided by the user.