RE: FW: [TEC] How to monitor the availability of TEC

Hi Simon,

 

Thanks, for the tip. Have not visited orb-data's website lately, should have ...i know...

 

Met vriendelijke groet/Regards,

Peter van Nes
BPCC Control Development / Product Development
Rabobank ICT  X

tel: +31 (0)30 21 52361
mail: P.Nes@xxxxxxxxxxxxxx

 

-----Oorspronkelijk bericht-----
Van: owner-tme10@xxxxxxxxxxxxxxxx [mailto:owner-tme10@xxxxxxxxxxxxxxxx]namens Simon Barnes
Verzonden: dinsdag 22 maart 2005 12:46
Aan: tme10@xxxxxxxxxxxxxxxx
Onderwerp: Re: [tme10] FW: [TEC] How to monitor the availability of TEC

Peter,

I have written resource models to monitor:

1.     Basic TEC State
2.     Number of Queued Events
3.     Number of Waiting Events
4.     Number of Parse Failed Events
5.     Time since last event

In many cases the simple TEC state alert does not pick up a TEC failure and I find that the "Time since last event" alert  which I have set to 15 minutes finds the problem. Initially my plan was to force an event to be sent every few minutes but in the environments I have installed these RMs in I have found that they were receiving events every few seconds anyway and a 15 minute gap was enough.

I wrote an article on this in our magazine -> http://www.orb-data.com/cgi-bin/launch.cgi?page=MessageBrokerIssue2

Regards,

Simon Barnes



Nes van, P (Peter) wrote:

Hi list,

 

Just curious...

 

How do you monitor the availability of your Tivoli environment?

 

When you have a single TMR environment with a separated TMR- and TECserver, your automated incident registration is connected to you TMR. Then the monitoring of the availability of your TEC is essential. What we need is an indication in case of unvailability of the TEC server.

When a TEC server is shutdown using the wstopesvr command a TEC_Stop event is generated which is visible on the TEC console. In this case you will get a notification that the eventserver is unavailable. In the sitiuation when the tec_* processes are killed (or aborted by a coredump) or the eventserver gets overflooded by events the console is unable to detect the unavailability.

This is because the TEC (java) console queries the DB directly and does not communicate with the tec_ui_server when no modifications are made to the interface by human intervention (acknowledgement / closing).

 

Has anyone found the ultimate solution, or does anyone know about future developments concerning TEC Console which wil deal with this problem?

 

Cheers,

 

 

Peter

 

 

 

================================================
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en
is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht
onterecht ontvangt, wordt u verzocht de inhoud niet te gebruiken en
de afzender direct te informeren door het bericht te retourneren.
================================================
The information contained in this message may be confidential
and is intended to be exclusively for the addressee. Should you
receive this message unintentionally, please do not use the contents
herein and notify the sender immediately by return e-mail.

-- 
Simon Barnes
Orb Data Ltd          Mobile: +44 (0) 7801 442035
Royal Albert House    Tel:    +44 (0) 1753 705 015
Sheet Street          Fax:    +44 (0) 1753 705 016
Windsor               Email:  mailto:simon.barnes@xxxxxxxxxxxx
Berkshire SL4 1BE     Web:    http://www.orb-data.com

================================================
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en
is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht
onterecht ontvangt, wordt u verzocht de inhoud niet te gebruiken en
de afzender direct te informeren door het bericht te retourneren.
================================================
The information contained in this message may be confidential
and is intended to be exclusively for the addressee. Should you
receive this message unintentionally, please do not use the contents
herein and notify the sender immediately by return e-mail.