Jane,

You may be interested in a project of mine:

http://dmon.org/zenticket.html

Obviously only for reference, it wouldn't directly work for what you're doing.  It's nice having the daemon though since I've been able to make it acknowledge events once it receives confirmation from our ticketing system that a ticket was generated.  If the generation was unsuccessful it tries again the following cycle.

It could fairly easily be modified to do whatever you need it to though, most of the code would work fine.  It does some things that would possibly be undesirable for you, such as using hardcoded filter rules to move events which don't meet the filters to history automatically.  It also continues to submit tickets every time the event count for an event increases in Zenoss (our ticketing system knows to increase a count value in the matching ticket instead of creating a new ticket).

It is designed to call on a script which does the actual ticket generation, it just passes the data over to the script (a perl script in our case) and the perl script passes data back to the daemon via stdout.  This allows us to maintain the perl script in one spot (an NFS share) without having to constantly upgrade the ticket daemon on all of our servers.

I can send you the actual ZenPack if you ever want to dig in and take a look.  PM me and I'll fire it over.

I would like to eventually adapt the daemon in to something a bit more generic.