IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Agent operation log
A Tivoli Enterprise Monitoring Agent can run autonomously for an undetermined period of time, taking data samples and saving events. Review the audit trail log to examine and review the agent activities, including while it was running autonomously.
When an agent runs autonomously, audit trail records for all events and true sampled application data rows are written to the operations log. The agent leverages the existing Agent Operation Log facility and outputs audit trail records to it. The Agent Operation Log can be viewed on the Tivoli Enterprise Portal while the agent is online.
- On distributed systems, the agent creates the Operation Log file automatically in the agent installation directory, names it ComputerName_product.LG0 for the current running log file, and renames the previous log file ComputerName_product.LG1 (the backup file).
- On z/OS systems, the agent writes the Agent Operation log records to a SYSOUT class, saving portions of records in memory cache.
The agent operations log also shows the activity of private situations.
The autonomous activity log record contains these fields:
- Agent system name
- Message ID: KRAIRA005
- Global timestamps, showing the actual local time of the event activity
- The message, which shows the situation name, application table name, system name, filter column name, filter value, and actual sampled value or event value. If the situation filter criteria specify several threshold name and value pairs and thus the output exceeds the operation log's record size, then the agent outputs multiple log records.
To obtain an agent autonomous operation activity report, create an Agent Operation Log custom query in the Tivoli Enterprise Portal that filters on message KRAIRA005, and then assign the query to a table view in a workspace at the agent level of the Navigator Physical view. Alternatively, you can assign the predefined query named Agent Operations Log to a table view and apply a post-filter through the Properties editor Filters tab filters out all rows except those with message KRAIRA005. shows a possible autonomous activity log that might result from such a query. This is the result of a table view of the Agent Operations Log filtered to include only the agent autonomy messages: == KRAIRA005
Server Name Message Number Global Timestamp Managed System Type Primary:East:NT KRAIRA005 02/16/2009 12:35:42 Situation NT_Process_CPU_Critical for KNT.WTPROCESS reset Primary:East:NT KRAIRA005 02/16/2009 12:34:43 Situation NT_Process_CPU_Critical for KNT.WTPROCESS triggered (03) Process_Name [_Total] value <kdsmain> Primary:East:NT KRAIRA005 02/16/2009 12:34:42 Situation NT_Process_CPU_Critical for KNT.WTPROCESS triggered (02) Priority_Base [0] value <8> Primary:East:NT KRAIRA005 02/16/2009 12:34:42 Situation NT_Process_CPU_Critical for KNT.WTPROCESS triggered (01) %_Processor_Time [65] value <66> Primary:East:NT KRAIRA005 02/16/2009 12:34:21 Situation NT_Log_Space_Low for KNT.WTPROCESS triggered %_Usage [95] value <100> Primary:East:NT KRAIRA005 02/16/2009 12:32:42 Situation NT_Process_Memory_Critical for KNT>WTPROCESS triggered (02) Working_Set [40000000] value <48832512> Primary:East:NT KRAIRA005 02/16/2009 12:32:41 Situation NT_Process_Memory_Critical for KNT>WTPROCESS triggered (01) Process_Name [_Total] value <Rtvscan> Primary:East:NT KRAIRA005 02/16/2009 12:31:21 Situation NT_System_CPU_Critical for KNT.WTSYSTEM triggered Operating_System_Version [5.0] value <5.1> Primary:East:NT KRAIRA005 02/16/2009 12:29:41 Situation CHECK_NETWORK_STAT for KNT.IPSTATS triggered (06) Datagrams_Received_Header_Errors [0] value <0> Primary:East:NT KRAIRA005 02/16/2009 12:29:41 Situation CHECK_NETWORK_STAT for KNT.IPSTATS triggered (05) Datagrams_Outbound_Header_Errors [0] value <0>
CTIRA_LOG_PATH agent environment variable for distributed enterprise monitoring agents specifies the directory where the agent's Operations Log file is stored (Windows <install_dir>\TMAITM6\logs; Linux and UNIX <install_dir>/config/logs.) The file names use the suffixes .LG0and .LG1.