'); $("#tabs").tabs({ selected: 1 }); $("#ic-homepage__ic-tips").append( quickTipHTML() ); unhideOneProductTip(); $("#ic-homepage__product-tips").wrapInner('
'); $("#ic-homepage__feed-tips").wrapInner('
'); });
IBM Tivoli Monitoring > Version 6.3 > User's Guides > Agent Builder User's Guide > Troubleshooting > Agent trace logs IBM Tivoli Monitoring, Version 6.3
Set RAS trace parameters
Pinpoint a problem by setting detailed tracing of individual components of the monitoring agent and modules.
To ensure that you understand log rolling and can reference the correct log files when you manage log file generation, see (Overview of log file management).
The Agent Builder agents and agent runtime use RAS1 tracing and generate the logs that are described in (Table 1). The default RAS1 trace level is ERROR.
Specify RAS1 trace options in the agent_nameENV file on Windows systems, and in the agentname.ini file on UNIX systems.
Procedure
Use one of the following procedures:
- Optional: Manually edit the configuration file to set trace log preferences:
- Open the file which contains the trace options.
On Windows: install_dir\TMAITM6\KPRODUCTCODEENV[_instance] or
install_dir\TMAITM6_x64\KPRODUCTCODEENV[_instance]
On UNIX: install_dir\config\productcode.ini for all new instances or
productcode[_instance name].config
- Edit the line that begins with KBB_RAS1= to set trace log preferences. For example, if you want detailed trace logs, set the Maximum Tracing option:KBB_RAS1=ERROR (COMP:kqz ALL) (UNIT:kra ALL)
- Edit the line that begins with KBB_RAS1_LOG= to manage the generation of log files:
- MAXFILES: the total number of files that are to be kept for all starts of a program. After this value is exceeded, the oldest log files are discarded. Default value is 9.
- LIMIT: the maximum size, in megabytes (MB) of an RAS1 log file. Default value is 5.
- IBM Software Support might guide you to modify the following parameters:
- COUNT: the number of log files to keep in the rolling cycle of one program startup. Default is 3.
- PRESERVE: the number of files that are not to be reused in the rolling cycle of one program startup. Default value is 1.
The KBB_RAS1_LOG parameter also provides for the specification of the log file directory, log file name, and the inventory control file directory and name. Do not modify these values or log information can be lost.
- Restart the monitoring agent so that your changes take effect.
- Optional: For Windows operating systems only, you can use the following alternative method to edit trace log parameters:
- Open the Manage Tivoli Enterprise Monitoring Services window.
- Right-click the icon of the monitoring agent whose logging you want to modify.
- Select Advanced > Edit Trace Parms. The Tivoli Enterprise Monitoring Server Trace Parameters window is displayed.
- Select a new trace setting in the menu in the Enter RAS1 Filters field or type a valid string.
- Modify the value for Maximum Log Size Per File (MB)to change the log file size (changes LIMIT value).
- Modify the value for Maximum Number of Log Files Per Session to change the number of log files per startup of a program (changes COUNT value).
- Modify the value for Maximum Number of Log Files Total to change the number of log files for all starts of a program (changes MAXFILES value).
- Optional: Click Y (Yes) in the KDC_DEBUG Setting menu to log information that can help you diagnose communications and connectivity problems between the monitoring agent and the monitoring server. The KDC_DEBUG setting and the Maximum error trace setting can generate many trace log messages. Use them only temporarily, while you are troubleshooting problems. Otherwise, the logs can occupy excessive amounts of hard disk space.
- Click OK. You see a message report a restart of the monitoring agent so that your changes take effect.
What to do next
Monitor the size of the logs directory. Default behavior can generate a total of 45 to 60 MB for each agent that is running on a computer. See the "Procedure" section to learn how to adjust file size and numbers of log files to prevent logging activity from occupying too much disk space.
Regularly prune log files other than the RAS1 log files in the logs directory. Unlike the RAS1 log files that are pruned automatically, other log types can grow indefinitely. For example, the logs in (Table 1) that include a process ID number (PID).
The following list comprises the RAS1 trace parameters settings:
- No error tracing. KBB_RAS1=-none
- General error tracing. KBB_RAS1=ERROR
- Intensive error tracing. KBB_RAS1=ERROR (COMP:kqz ALL)
- Agent interaction with the Tivoli Enterprise Monitoring Server. KBB_RAS1=ERROR (UNIT:genericagent ALL) (UNIT:kra ALL)
- Trace data collection. KBB_RAS1=ERROR (UNIT: ALL)
- Trace Script data collection. KBB_RAS1=ERROR (UNIT:shell ALL) (UNIT:commandwithtimeout ALL)
- Trace Availability data collection. KBB_RAS1=ERROR (UNIT:availability ALL) (UNIT:winavailability ALL)
- Trace Windows Event Log data collection. KBB_RAS1=ERROR (UNIT:winlog ALL) (UNIT:eventlog ALL)
- Trace log file data collection. KBB_RAS1=ERROR (UNIT:logmonitor ALL)
- Trace SNMP data collection. KBB_RAS1=ERROR (UNIT:snmp ALL)
- Trace ICMP Ping data collection. KBB_RAS1=ERROR (UNIT:ping ALL)
- Trace CIM data collection. KBB_RAS1=ERROR (UNIT:cim ALL)
- Trace PerfMon data collection. KBB_RAS1=ERROR (UNIT:queryclass ALL)
- Trace WMI data collection. KBB_RAS1=ERROR (UNIT:wmi ALL)
- Trace separate collector interface. KBB_RAS1=ERROR (UNIT:custom ALL) (UNIT:CPS_Socket ALL) (UNIT:cpci ALL)
The KDC_DEBUG setting and the Maximum error trace setting can generate many trace logs. Use them only temporarily, while you are troubleshooting problems. Otherwise, the logs can occupy excessive amounts of hard disk space.
Parent topic:
Agent trace logs