I could probably do this with an ugly hack to my sendmail local
delivery rules, but I would really like a third alerting option, "send to pipe". Or even execute arbitrary commands here, as we can with Event Commands, but with the email header already created.

Extra bonus points if you supply all the TALES-available variables to the shell environment.

I want to use SEC to aggregate alerts, but retain all the power of Zenoss' built-in event mapping and alert filters. Eventually I hope to come up with some tools to autogenerate SEC configs, with heirarchies of SEC "Contexts" based on layer-2 topologies and service dependencies. I'm guessing that Zenoss could do something like this in a day, and give the user community a hook we can use to mitigate our alert storm problems while you work on a better internal solution.

Thanks.


--
    *Not speaking on behalf of my employer unless otherwise noted*
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to