Quick Feature request
Service Intelligence
By that I mean, under certain circumstances allow services to go above
threshold levels..
So for example, if a process x is running on a database server allow CPU
to go above y
You could also say
If a reload process is happening on server x allow http to not alert
Just an idea that came to me while discussing batch job load on a
database server that one of our teams is using. Where a specific batch
job could send the cpu load high and that is expected, but the batch job
isn't scheduled and is just run as and when. But the control has to be
fairly fine grained to stop the server not alerting when there is an
issue.
Mike Rowell
Systems Team Leader
* Email: user-63f3e97eb1de@xymon.invalid
* Tel: XXX XXXX XXXX
* Fax: XXXX XXX XXXX
www.rightmove.co.uk <http://www.rightmove.co.uk/>; - the UK's number 1
property website
This message (including any attachments) is confidential and may be
legally privileged. The content and views expressed are those of the
sender and not necessarily Rightmove plc. If you are not the intended
recipient, you must not disclose, copy or use any part of it. Please
delete all copies immediately and notify the sender. Rightmove plc is
registered in England and Wales, No. 03997679. Registered Office:
Rightmove plc, Grafton Court, Snowdon Drive, Milton Keynes, MK6 1AJ.
This email has been scanned for all viruses by the MessageLabs service.