Well, I was going to recommend zensendevent as an alternative... Maybe check the Zenoss Dev forum? I'm not a developer, so I don't know, but some users have been using SOAP or various APIs... -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University
dberger wrote, On 4/22/2009 4:13 PM: > Wow. That gives me the choice of the entire dev tutorial or the entire > project documentation. Does that mean that the simplest way to support third > party event messaging protocol is to implement it myself? Is there a known > facility for this? > > I guess if I haven't made myself quite clear about my actual goal, it would > be about as simple as executing a system call like this > > > Code: > zensendevent -c /MyApp/Fail -p Monitor -s Critical Onos\! very bad message\! > > > > My understanding is that this has to be executed locally by the user who has > installed zenoss. My goal would be to do this remotely. Worst case > scenario, I'll implement a listener on some port that takes arguments for > class, program, level, summary, and message and just executes a system call > locally. However, if there is a standard feature that gets this done, I'd be > excited to hear about it. > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://forums.zenoss.com/viewtopic.php?p=33705#33705 > > -------------------- 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
