I certainly understand the possibility of being overwhelmed, and how to mitigate that, perhaps by controlling which kinds of repairs (for some definition of "kind") might send such alerts. My biggest concern is just how to approach this issue. I definitely want to know when systems are fixing things, especially if they're fixing the same thing over and over, at which point we'd investigate the underlying issue. A single repair may or may not require investigation, depending on the nature of the repair.
What mechanism did you use to send such alerts? Thanks, Justin -----Original Message----- From: nwat...@symcor.com [mailto:nwat...@symcor.com] Sent: Tuesday, January 19, 2010 1:35 PM To: Justin Lloyd Cc: help-cfengine; help-cfengine-boun...@cfengine.org Subject: Re: Triggering an alert when repairs occur You can do this. I've done it myself. However, you can overload yourself with useless alerts. e.g. ALERT: Cfengine doing it's job! Tongue in cheek to be sure but you get the point. It is however not a bad idea to log the repair, quietly. Sincerely, -- Neil Watson 416-673-3465 This electronic communication and any attachments may contain confidential and proprietary information of DigitalGlobe, Inc. If you are not the intended recipient, or an agent or employee responsible for delivering this communication to the intended recipient, or if you have received this communication in error, please do not print, copy, retransmit, disseminate or otherwise use the information. Please indicate to the sender that you have received this communication in error, and delete the copy you received. DigitalGlobe reserves the right to monitor any electronic communication sent or received by its employees, agents or representatives. _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
