[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Integrating Hobbit with Ticketing system(s) / Feature Request
- To: hobbit (at) hswn.dk
- Subject: Integrating Hobbit with Ticketing system(s) / Feature Request
- From: Charles Jones <jonescr (at) cisco.com>
- Date: Mon, 14 Jan 2008 10:05:24 -0700
- Authentication-results: sj-dkim-4; header.From=jonescr (at) cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; l=1416; t=1200330326; x=1201194326; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jonescr (at) cisco.com; z=From:=20Charles=20Jones=20<jonescr (at) cisco.com> |Subject:=20Integrating=20Hobbit=20with=20Ticketing=20syste m(s)=20/=20Feature=20Request |Sender:=20; bh=sDTwODL7tIF/Ml3nWLS/bAGYNqvixp1HiW+drA7OqMw=; b=OFgFCAOTdmjKKb8INOaq6+S0lio6zzis4uC76VHWzVdktISfoy1zmiyauH 8P7TiCXLslVDZCRfrTU4qb+1G6RqKiUyYzwnaV+cad19K6PujfnZa57JItXg TUBEqP7fwT;
- User-agent: Thunderbird 2.0.0.9 (X11/20071115)
Some time ago (years actually), I integrated Big Brother with "Request
Tracker", which is a popular open source helpdesk ticketing system. This
was done by CCing hobbit alerts to the ticketing system, and the
creation of a custom plugin that parsed the incoming mails and
automatically created a ticket for red alerts. The plugin was "smart"
enough so that when a recovery message arrived, it would auto-resolve
the initial ticket created from the first alert.
I am now looking again at integrating Hobbit with a ticketing system,
but this time with "Jira" (http://www.atlassian.com/software/jira/).
Jira has a very useful API as well as an RCP/SOAP interface, so doing
something similar to what I did with RT should be relatively simple.
However, in going over the code in my head (I havn't written it yet), I
see a problem. I believe that Hobbit is different from BB in that
recovery pages are not sent with an ID (and I think if you forced it
with a script the ID is "-1") which makes it impossible to relate them
to the origional alert. Is there any simple way that we could have
access to this ID number, or does Hobbit simply not track it?
Otherwise I may have to do something like query hobbitboard and look for
a hostname.service that matches the resolved message, and I'd rather not
do that as it will just slow things down and add extra complexity.
-Charles