Steps to demonstrate functionality
- Using a windows batch file which outputs sample numerical values in a line . We will match columns 2 , 3 and 4 on each line for threshold breach. Configure a new logmon profile to execute the batch file say every 20 seconds.
2. Configure a new logmon profile to execute the batch file say every 20 seconds. This is test600 in this example
3. Configure a new logmon profile to execute the batch file say every 20 seconds. This is test600 in this example
4.Create a Watcher Rule
In the Watcher Rules tab -> Standard tab of the rule -> Match Expression field, specify the expression to match in the command response.
For example, specify /test.*/ to match for lines with this string.
5. Configure Custom Variables in Watcher Rule
You can configure custom variables and use the variable in the alarm message text. You can also configure QoS messages for these variables.
Follow these steps:
- In the Variables tab, create a variable. For example, create a variable var1 that extracts the value from column 2 and checks if this exceeds specified threshold
2. Repeat the above for new var2 and var3 variables to extract column 3 and column 4 from each line containing string test
6. Configure the Watcher Rules -> Alarm ->Variables Exceed Alarm ->Minimum Match Count and Alarm text
Minimum Match Count: Define the minimum number of times the threshold breach for all defined variables must occur for the probe to generate the alarm.
Severity: Define the severity of the alarm. The probe will generate the alarms only for the defined severity. If you do not define any minimum match count value and severity, the probe sends the default message defined in the Standard section.
Suppression Key: Define the suppression key to avoid multiple instances of the same alarm
7. Alarm is now generated by logmon as thresholds are breached for configured check interval
Alert Details as seen in Dr Nimbus