IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Situation event integration with Tivoli Enterprise Console > Synchronize situation events
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Close sampled events
When a situation event from a sampled situation is forwarded to the IBM Tivoli Enterprise Console event server and that event is subsequently closed in the event server, the behavior of event synchronization is to send a request to the Tivoli Enterprise Monitoring Server to acknowledge the situation with a specified timeout. The reason for this is because closing events from sampled situations causes problems with the situation's ability to fire after the close in IBM Tivoli Monitoring.
If the acknowledgment of the situation expires and the situation is still true, then a new situation event is opened in the IBM Tivoli Enterprise Console. If the situation becomes false, then it resets itself in IBM Tivoli Monitoring and the event remains closed in the IBM Tivoli Enterprise Console.
The default acknowledgment expiration time is 59 minutes. This can be changed in the situation timeouts configuration file on the event server (sit_timeouts.conf). Also, expiration times for individual situations can be configured in this file. After editing this file, you can have the expire times dynamically loaded into the IBM Tivoli Enterprise Console rule using the sitconfig.sh refresh command in $BINDIR/TME/TEC/OM_TEC/bin.
Parent topic:
Synchronize situation events