I've successfully tested monitoring for the appearance of a statically defined file (i.e. no wildcards), and have been happy with the result.
I'm now tasked with trying to alarm on the appearance of file where only part of the filename will be static, hence the need for wildcards.
I'm at the point where the presence of a file causes a green condition, and the removal of that file causes a white condition.
The client-local.cfg is set up to look like this (the commented lines are my various attempts to test/change the behavior):
file:find /opt/WSCluster*/WebSphere/wp_profile | grep javacore | sort -r
#file:find /opt/WSCluster*/WebSphere/wp_profile | grep javacore | sort -r | head -n 1
#file:find /opt/WSCluster1/WebSphere/wp_profile | grep javacore | sort -r | head -n 1
#file:find /opt/WSCluster2/WebSphere/wp_profile | grep javacore > /dev/null | sort -r | head --lines=1
#file:find /opt/WSCluster3/WebSphere/wp_profile | grep javacore > /dev/null | sort -r | head --lines=1
log:/var/adm/syslog/syslog.log:10240
The analysis.cfg is set up like so (again, commented lines are my attempts to test/change the behavior):
FILE /opt/WSCluster1/WebSphere/wp_profile/%javacore(^*.) yellowNOEXIST
FILE /opt/WSCluster(^*.)/WebSphere/wp_profile/javacore(^*.)
NOEXIST yellow
FILE /opt/WSCluster(^*.)/WebSphere/wp_profile/javacore(^*.)
yellow
I've put a test file out, /opt/WSCluster1/WebSphere/wp_profile/javacore.mike1, and Xymon is reporting green on the file's existence...which, of course, is not the desired behavior.
My guess is that I'm completely bollixing the regex...any thoughts or help would be appreciated.
--
Mike Burger
AIX Administrator
<http://freedomhome.fhmc.local/intranet/main.jsp>
Phone (317) 537-3680, Fax (317) 537-4680, Cell (317) 797-2040
E-mail: Mike.Burger at FreedomMortgage.com <mailto:Anthony.House at freedommortgage.com>
"Once word leaks out that a pirate's gone soft, people begin to disobey you and then it's nothing but work, work, work, all the time." --Westley/The Dread Pirate Roberts
CONFIDENTIALITY NOTICE: This e-mail message, including all attachments, is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure, alteration or distribution is strictly prohibited and may violate state or federal law. If you are not the intended recipient, please contact the sender by reply e-mail, delete this email and destroy all copies of the message.