I cannot fathom why it repeats at all so rather that look for something that isn't there I have forced every alert to repeat every seven days to see if that resolves the issue!
|\/|
--
Martin Ward
Manager, Technical Services
Service Operations
DDI:+44 (0) 20 7863 5218 / Fax: +XX (X)XX XXXX XXXX / www.colt.net
Colt Technology Services, Unit XX, Powergate Business Park, Volt Avenue, Park Royal, London, NW10 6PW, UK.
Help reduce your carbon footprint | Think before you print. Registered in England and Wales, registered number 02452736, VAT number GB 645 4205 50
-----Original Message-----
From: user-ce4a2c883f75@xymon.invalid [mailto:user-ce4a2c883f75@xymon.invalid]
Sent: 04 March 2013 11:27
To: Ward, Martin
Cc: xymon at xymon.com
Subject: Re: [Xymon] Xymon alerting when it's been told not to
On Mon, 4 Mar 2013 09:19:25 +0000, "Ward, Martin"
<user-2d33a6eb6a05@xymon.invalid>
wrote:
Hi all,
I have the following in my alerts.cfg:
[snip]
Yet I am still getting CPU alerts from ivma2.lon.osspriv.colt.net
Try running
xymoncmd xymond_alert --test ivma2.lon.osspriv.colt.net cpu and look for
lines like
00004226 2013-03-04 12:24:11 Matching host:service:dgroup:page
'cscxymweb3.csc.dk:disk:Xymon
servers:cscdk/mwsmonitor,cscdk/mwsmonitor'
against rule line 1260
00004226 2013-03-04 12:24:11 *** Match with 'MAIL $XYMONADM
$XYMONADMREPEAT' ***
00004226 2013-03-04 12:24:11 Mail alert with command '/usr/bin/mail -s
"Xymon [12345] cscxymweb3.csc.dk:disk CRITICAL (RED)"
user-fe4cb829cfaa@xymon.invalid'
00004226 2013-03-04 12:24:11 Matching host:service:dgroup:page
'cscxymweb3.csc.dk:disk:Xymon
servers:cscdk/mwsmonitor,cscdk/mwsmonitor'
against rule line 126
to see which rule triggers the alert.
Regards,
Henrik
[Colt Disclaimer]
This email is from an entity of the Colt group of companies.
Colt Group S.A., K2 Building, Forte 1, 2a rue Albert Borschette, L-1246 Luxembourg, R.C.S. B115679.
Corporate and contact information for our entities can be found at
http://colt.net/uk/en/Colt-Group-of-Companies/index.htm.
Internet communications are not secure and Colt does not accept
responsibility for the accurate transmission of this message. Content
of this email or its attachments is not legally or contractually binding
unless expressly previously agreed in writing by Colt