Useful Events Mapping to Logs entry and SNMP

Useful Events Mapping to Logs entry and SNMP

book

Article ID: KB0093261

calendar_today

Updated On:

Products Versions
TIBCO DataSynapse GridServer -
Not Applicable -

Description

Resolution:
Note: The format of the dateTime is MM/dd/yy HH:mm:ss.S, and the format of the levelLog is Finest, Finer, Fine, Config, Info, Warning, Severe.
Useful Events mapped from Logs entry for Tivoli or HP OpenView.
Events Name    Log Event    Log Location    Explanation
Driver Added    &ltdateTime_ levelLog>: Driver:&ltHostName/UserNameClient>:Added    Broker    
Driver Removed    &ltdateTime_ levelLog>: Driver:&ltUSERNAME>:Removed    Broker    
Engine Added    &ltdateTime_ levelLog>: EngineDaemon:&lthostName>-&ltIP>:Added    Broker    
Engine Removed    &ltdateTime_ levelLog>: EngineDaemon:&lthostName>-&ltIP>:Removed:Code:&ltvalue>    Broker    
Engine Died    &ltdateTime_ levelLog>: Engine Daemon:&lthostName>-&ltIP>:Died    Broker    
Job Cancelled    &ltdateTime_ levelLog>: JobId:&ltSERVICEID>-&ltSERVICEID>:CancelledJob    Broker    
Job Finished    &ltdateTime_ levelLog>: Driver:&ltSERVICENAME>:CompletedService:&ltSERVICENAME>-&ltSERVICEID>    Broker    
Server Started    &ltdateTime_ levelLog>: Message Server has started.    Broker    
Task Error    (autopack off)
&ltdateTime_ levelLog>: Engine:&lthostName>-&ltinstanceNbr>:TaskCompleted:&ltserviceName>-&ltserviceID>-&lttasksID>
&ltdateTime_ levelLog>: &ltserviceName>-&ltserviceID>-&lttaskID>, Task failed due to : &ltException>: Throw Exception to fail task. on Engine: &lthostName>

( autopack on )
&ltdateTime_ levelLog>: Engine:&lthostName>-&ltinstanceNbr>:TaskCompleted:&ltserviceName>-&ltserviceID>-&lttasksID>
&ltdateTime_ levelLog>: &ltserviceName>-&ltserviceID>-&lttaskID>, &ltException>: Throw Exception to fail task., subtask number &ltnbr>    Broker    Two Entries are needed to determine which Engine is associated to which failed task. The Error Message is slightly different when using the Autopack option.
Broker Added    &ltdateTime_ levelLog>: Broker:http://&lthostName>:&ltport>/livecluster-&ltbrokerName>:Added
Director    
Broker Removed    &ltdateTime_ levelLog>: Broker:http://&lthostName>:&ltport>/livecluster-&ltbrokerName>:Removed
Director    
Broker Died    &ltdateTime_ levelLog>: Broker:http://&lthostName>:&ltport>/livecluster-&ltbrokerName>:Died
Director    
EngineDaemon Added    &ltdateTime_ levelLog>: EngineDaemon:&lthostName>-&ltIPAddress>:Added    Director    
EngineDaemon Removed    &ltdateTime_ levelLog>: EngineDaemon:&lthostName>-&ltip>:Removed:Code:&ltvalue>    Director    
EngineDaemon Died    &ltdateTime_ levelLog>: Engine Daemon:&lthostName>-&ltip>:Died    Director    
Remote Database Backup Failure    &ltdateTime_ levelLog>: problem backing up db to &ltBase Dir>/webapps/livecluster/WEB-INF/db/internal/backup &ltException>
&ltdateTime_ levelLog>: Scheduling network backup (0) at location http://&lthostName>:&ltport>/livecluster/director/DatabaseNetworkBackupPlugin?internal=&ltID>
Director    Failure to backup the secondary internal DB
Local Database Backup Failure Event    &ltdateTime_ levelLog>: problem backing up db to &ltErrorMessage>
&ltdateTime_ levelLog>: Failed to backup database &ltException>    Director    Failure to backup the primary internal DB
Server Started    &ltdateTime_ levelLog>: Message Server has started    Director    
Driver Initial Task Submitted    &ltdateTime_ levelLog>: Driver:&ltHostName/UsernameClient>:SubmittedTasks:&ltServiceName>-&ltServiceID>:Amount:0    Broker    First Task of the Service
Driver Subsequent Task Submitted    &ltdateTime_ levelLog>: Driver:&ltHostName/UsernameClient>:SubmittedTasks:&ltServiceName>-&ltServiceID>:Amount:1    Broker    other Tasks
Driver Task Collected    &ltdateTime_ levelLog>: Driver:&lthostName/UserNameClient>:CollectedTasks:&ltserviceName>-&ltserviceID>:Amount:1    Broker    Task Collected by the Driver for a specific Service
Driver State Update    &ltdateTime_ levelLog>: Driver:&lthostName/UserNameClient>:UpdateState:&ltserviceID>    Broker    Update to the State for the Service
Engine LogOff    &ltdateTime_ levelLog>: Engine:&lthostName>-&ltinstanceNbr>:Logoff:&ltReasonForLogOff>    Broker    An engine can LogOff for multiple reasons: 1. Native daemon shut down the Engine 1. Restarting to load librar 1. Rerouted by the Engine Balancer 1. etc...
BlackListing Engine    &ltdateTime_levelLog>: blacklisting engine &ltHOSTNAME>-&ltINSTANCE> for Service &ltSERVICEID>-&ltSERVICEID>    Broker    
Primary Down    &ltdateTime_levelLog>: Broker:http://&lthostname>:&ltport>/livecluster-&ltbrokerName>:LoggedOff:&ltIPPrimary>:&ltport>
&ltdateTime_levelLog>: Will try to relogin to &ltIPPrimary>:&ltport>
&ltdateTime_levelLog>: Sending login message on &ltIPPrimary>:&ltport> {x Times}
&ltdateTime_levelLog>: Logged in to &ltIPPrimary>:&ltport>
&ltdateTime_levelLog>: Broker:http://&lthostname>:&ltport>/livecluster-&ltBrokerName>:LoggedIn:&ltIPPrimary>:&ltport>
Broker    The message {&ltdateTime_levelLog>: Sending login message on &ltIPPrimary>:&ltport>} repeated Multiples times over the period of time Primary Down
Primary Down    &ltdateTime_levelLog>: Will try to relogin to &ltIPPrimary>:&ltport>
&ltdateTime_levelLog>: Sending login message on &ltIPPrimary>:&ltport>
&ltdateTime_levelLog>: Logged in to &ltIPPrimary>:&ltport>
&ltdateTime_levelLog>: Secondary logged into the Primary, so logging off Deamons    Secondary    The message {&ltdateTime_levelLog>: Sending login message on &ltIPPrimary>:&ltport>} repeated Multiples times over the period of time Primary Down.
Secondary Down    &ltdateTime_levelLog>: Broker:http://&lthostname>:&ltport>/livecluster-&ltBrokerName>:LoggedOff:&ltIPSecondary>:&ltport>
&ltdateTime_levelLog>: Will try to relogin to &ltIPSecondary>:&ltport>
&ltdateTime_levelLog>: Sending login message on &ltIPSecondary>:&ltport>
&ltdateTime_levelLog>: Logged in to &ltIPSeconday>:&ltport>
&ltdateTime_levelLog>: Broker:http://&lthostName>:&ltport>/livecluster-&ltBrokerName>:LoggedIn:&ltIPSecondary>:&ltport>
Broker    The message {&ltdateTime_levelLog>: Sending login message on &ltIPSecondary>:&ltport>} repeated Multiples times over the period of time Primary Down.
Server Shutdown    &ltdateTime_levelLog>: Shutting down Message Server.
&ltdateTime_levelLog>: Shutdown reason: &ltReason>    Director    These Message will be logged only if the manager is shutdown correctly.
If the Manager's JVM dies for any reasons you will not see these messages.
Server Shutdown    &ltdateTime_levelLog>: Shutting down Message Server.
&ltdateTime_levelLog>: Shutdown reason: &ltReason>    Broker    These Message will be logged only if the manager is shutdown correctly.
If the Manager's JVM dies for any reasons you will not see these messages.
Note: The format of the dateTime is MM/dd/yy HH:mm:ss.S, and the format of the levelLog is Finest, Finer, Fine, Config, Info, Warning, Severe.

Issue/Introduction

Useful Events Mapping to Logs entry and SNMP