Archived community.zenoss.org | full text search
Skip navigation
26630 Views 2 Replies Latest reply: Jan 31, 2010 11:12 AM by Ryan Matte RSS
jcurry ZenossMaster 1,021 posts since
Apr 15, 2008
Currently Being Moderated

Jan 19, 2010 4:51 PM

Zenoss / IBM Tivoli Event Console (TEC) integration

I have been doing some work to forward events from Zenoss to IBM's Tivoli Event Console (TEC) product.  I have two working methods, one of which uses Zenoss event commands and the other is a bit of a cheat using Zenoss pager alerts but it works quite nicely.

 

On the TEC side, I have done work to create a Zenoss source, Zenoss event group for console viewing, and a rudimentary baroc class and rules files to interpret and process the Zenoss events in TEC, including duplicate detection and a "good news closes bad news" rule.

 

I don't know whether this is of interest to folks???

 

I am not going to write up a full paper if there are only two people on the planet that are interested.  Please indicate here if you would be interested.

 

Cheers,

Jane

  • Ryan Matte ZenossMaster 653 posts since
    Mar 26, 2009
    Currently Being Moderated
    2. Jan 31, 2010 11:12 AM (in response to jcurry)
    Re: Zenoss / IBM Tivoli Event Console (TEC) integration

    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.

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points