Update on this. The problem appears to be one of container logic. The SQL for the device class selection seems to have gone from subtree inclusive (deviceClass = '/Server%') to literal (deviceClass = '/Server'). So if someone cares about all of the stuff in /Server, they have to list off EVERY subclass they care about (painfully, even if deeply nested). It used to be that, for example, '/Network' would match '/Network/Switch/Cisco' but now we have to explicitly say '/Network/Switch/Cisco' ... Perhaps I'm very mistaken, but this seems to have changed.
Turning zenactions up to debug 10 and looking at the SQL confirms that's how it's working currently. The only question is whether I'm wrong about how it used to work (which I obviously don't think I am, but it can happen). On Thu, 2007-08-16 at 13:43 -0400, Matthew Keller wrote: > I'm having this problem now with a 2.0.3 -> 2.0.4 upgraded system. Those > of us with rules that have existing since 2.0.3 seem ok, but rules added > - even by "managers" for 2.0.4 seem to be skipped entirely. ZenActions > isn't firing anything to them. > > On Thu, 2007-08-09 at 18:05 +0000, db404 wrote: > > Hi, > > > > Having problems with a fresh install of 2.0.4. Devices are monitoring > > correctly, I have one (non-admin) user setup, clicking 'test' for send > > email on the user results in a test email being sent and received correctly. > > > > However if I set up a simple alerting rule (basically just defaults with > > active set to true) no emails are received when a host fails. I've also > > tried a couple of other things (e.g. adding a schedule) with no success. > > > > Where would I start looking to debug this issue? > > > > I had alerts working on 2.0.3 (before wiping and reinstalling 2.0.4) - but > > on 2.0.3 I was getting issues with multiple 'CLEAR' messages being sent, > > hence the re-install. > > > > > > > > > > -------------------- m2f -------------------- > > > > Read this topic online here: > > http://community.zenoss.com/forums/viewtopic.php?p=9756#9756 > > > > -------------------- 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 _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
