I doubt it, it is an enhancement request. But if you code it, you might look into contributing it to Zenoss... -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University
zarxcky wrote, On 1/23/2009 2:32 AM: >> I was looking at something similar yesterday. Although the standard >> zensendevent command only supports the fields you document, it is not a >> complicated piece of Python. If you make a copy of it (it's in $ZENHOME/bin) >> then modify the code, I think you can have zensendevent generate whatever >> fields you want - I modified it to include agent. Just copy an existing pair >> of lines to parse your new argument and the couple of lines that set the >> appropriate event field. >> > > > Thanks Jane, > > I have seen the zensendevent tool source code and I think it is easy to > implement the idea of yours. I'll try your idea later when I have free time > (to add eventKey field to the zensendevent) or perhaps if Zenoss developer > see this thread, to add it to their 2.3.3 enhancement list.. > > Now I wonder if this can be called a bug.. > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://forums.zenoss.com/viewtopic.php?p=30408#30408 > > -------------------- 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
