ADSM-L

Re: Tivoli TEC Monitoring

1998-09-09 10:40:29
Subject: Re: Tivoli TEC Monitoring
From: Kells Kearney <kells AT WINTERLAND.MAINLAND.AB DOT CA>
Date: Wed, 9 Sep 1998 08:40:29 -0600
Phil Chissell wrote:

> ADSM V3 on NT Server 4.0 SP3.
>
> Is anybody out there using Tivoli with ADSM?

      I've used TEC before, using it to consolidate events and
sortthrough them.  But, haven't set up a TEC server and forwarded events
into TEC (yet!).

> We are using the new ADSM V3 functionality of sending ADSM events
> directly to the TEC server by using the "begin eventlogging tivoli"
> command.  This seems to work OK but whenever the TEC server goes
> down/gets restarted etc., it also seems necessary to restart the ADSM
> Server else we don't receive any more events.
>
> Has anybody else encountered this problem or know of a solution?

    A very nasty problem.

   The only thing I can suggest (it's ugly, but...) is to use ADSM to
send events
to an external program, and then run a script to slice and dice the
output, and then
run the TEC command line program (can't for the life of me remember what
the
name of it is --- been away from TEC too long! :) to send the output to
the TEC
server.  I haven't looked at the output of the ADSM event stream to see
how
simple it is to put it into severities etc, but you will definitely need
to do some
processing in order to get it into the proper format.  By viewing the TEC
logs,
you can find out what the fields of the event were, and fake them out in
your
script.

   The problems with the above approach are:
 - use of more processes to accomplish the same thing (a fork/exec for
    every message that makes it through the ADSM filter)
 - more work to set it up

   The nice things about the above approach are:
  - it will work all the time :)  If taking down the server all the time
doesn't appeal
    to you, you can use this as a stop-gap approach until this gets
patched.
  - the script can be much more customized, and you can do more text
processing
    or field breakout inside your script.  In earlier versions of TEC,
text manipulation
    was non-existent, so formatting a message involved a fork/exec to
parse the message,
    and THEN re-submit the message as a new event.  UGLY! UGLY! UGLY!

  Suggestion, use perl as the scripting language -- it will make your
life MUCH
easier.

  Hope this helps!


kells
<Prev in Thread] Current Thread [Next in Thread>