On Apr 11, 2008, at 3:45 PM, jpertschuk wrote:
We have the MySqlMonitor running. The one that comes standard with the install. By default it's set up with a severity of error. All of our groups are set up to only page when something critical happens. Rules really are setup correctly. We got "many connection errors; unblock with 'mysqladmin flush-hosts" sent out as critical. Suggesting that the host that zenoss was probing had too many connection errors from zenoss and then blocked zenoss. This then triggered a critical alert somehow, which makes no sense to me since the severity on the MysqlMonitor template is set to error only and rules are setup correctly--this never happens with anything else. How did is happen so that a critical error was generated and when can I go to edit this. I don't mind editing the script (if I can find where it lives)if it can't be fixed in the GUI. I don't mind that it generated an error it's just that going critical pages people this is not something people needed to be woken up at 3AM for. W e had to disable the tempalte to prevent this until we know how/why this happened.
When one of these monitoring plugins exits with a code of 2 (instead of 1) it will bump the severity up one level from what it is set to in the data source. I'd bet that the plugin exited with a code of 2.
_______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
