I'm currently deploying Zenoss on my servers and configuring the differents templates, but I'm troubled by some "problems".
Why is a dedupip using criticity level? If you set a threshold with escalate count, you'll get 2 differents alerts for the same problem. I would find much better that a new event with a higher criticty (matching eventclass key and so on) replace the former one, moving it to the history. I also think that there should be more informations in events details. When an events occurs, you only get the message from the first occurence. It could be good to have, in the comments for example, the history of the differents message received. To see in a glimpse if things are getting better or worse. I also have some practical question: - Is it possible on a new events to clear some and add a new one. Example: My mail server is not answering anymore on IMAP, POP and SMTP pop. So i get 3 new alerts. Then I get a new alert telling that the server is down (not answering to ping). I would like to clear the "services" alerts and add a new one telling my server is down. I looked a bit around but couldn't manage to find an answer. - How does zenoss create events when executing a command (local or remote)? Is it by parsing returned values, or by getting the exit status code of the command? - I intend to monitor some log files using libexec/check_log. When an error occurs, check_log will return whatever is needed so zenoss generates an event. But the next time I'll run check_log, this error won't be here anymore, so zenoss may send a clear event that'll move to history the previous one, thus making it difficult to know there has been a problem. Am I wrong? If not, what is the right way to monitor log file (not using syslog) Thanks in advance Nicolas Morey-Chaisemartin -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=8920#8920 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
