Thanks Jon,
I've copied you profile and applied it to mine but I'm getting some strange results. It keep alarming reporting that the words "No" or "Yes" has not been found, even though those keywords are in my file..
My first thought was to use the "Match on every run" option, which apparently reverses the standard logic of Logmon, see this video from 2 minutes 30 seconds in.
The logmon Probe (Part 2 of 3) - Nimsoft Monitor - YouTube
Even using this option I still get alarm reporting that the keywords are absent, even though they are present in the file..
I'm confused!
Here's my profile:
<CMP Roamed Calls>
active = yes
interval = 30 sec
scanfile = /output/Roamed_Calls_%Y-%m-%d.csv
scanmode = updates
alarm = yes
qos = no
message = no
user =
monitor_exit_code = No
max_alarm_sev = 5
max_alarms =
max_alarm_msg =
password =
subject =
fileencoding =
resetFile = yes
initialfileptr = 2
resumefileptr = 4
command_timeout_active = no
command_timeout =
command_severity = 2
command_timeout_alarm =
<watchers>
<No-Yes>
active = yes
match = /(Yes)/
level = warning
subsystemid =
message = HELP! No or Yes NOT found!
i18n_token =
restrict =
expect = yes
abort = no
sendclear = no
count = no
separator =
suppid =
source =
target =
qos =
runcommandonmatch = no
alarm_on_first_match = no
commandexecutable =
commandarguments =
timeout = 1
count_operator = lt
count_threshold = 1
pattern_threshold =
expect_message = No or Yes HAS been found
expect_level = clear
</No-Yes>
</watchers>
</CMP Roamed Calls>