First, i realize that this alert function probably carried over from BB. It's a handy alert to have for any monitored client that inadvertently reboots. Is there any way to configure this check for those occassions when the the reboot is planned?
For example, we schedule maintenace on 30 systems. Works great, howeer as each system recovers from the required reboot (or is powered back on), we have 60 minutes of email warnings in the case when we actually alert for CPU (Windows systems here). it's easy enough to acknowledge the reboot in the event that the technicians aren't trying to resurrect the one system that failed to recover. In the case where we don't alert on CPU at all (most Unix systems), we don't have an acknowledgement code to relieve the warning. The problem here is that our customer support group sees the web display and automatically thinks we're not aware of what might have been a potential problem.
Any thoughts?
participants (1)
-
sblee@tazmania.org