|
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.
| 