I'm not sure how to explain it better, I think you understand it. Alerts are separate from events, and I think it's a good thing. When different users need to know about different failure modes of a server, it's nice to be able to separate out alerts.
For instance, I don't need to be alerted that a license manager is down on ServerX, but I do need to be alerted if ServerX is down. I manage the OS/Server hardware, and my colleague manages the License Server app. For the Zenoss server, I manage Zenoss, but another colleague manages the Linux OS and hardware... So that may explain why it works the way it does. Basically, you may also not want alerts on every event that comes in, so you can filter a second time on the alerting rules. I hope this helps? -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University dveezy wrote, On 8/25/2009 11:11 AM: > Is this serious that you have to create new "user" groups, then assign them > monitoring to specific devices in order for alerting to work? > > You can't go server by server and just assign monitoring alerts through there? > > If so that seems like a huge flaw in the product as the administrative > overhead of creating the user groups and rules would be insanely time > consuming, whereas a product like Nagios you can just assign alerting > addresses through the server, or process itself. > > Could someone help me better understand this? > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://forums.zenoss.com/viewtopic.php?p=38383#38383 > > -------------------- m2f -------------------- > > > > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
