IBM Tivoli Monitoring > Version 6.3 > User's Guides > Agentless OS Monitor User's Guides > Agentless Monitoring for HP-UX User's Guide > Troubleshooting > Trace logging > RAS trace parameters IBM Tivoli Monitoring, Version 6.3
Set RAS trace parameters using the GUI
On Windows systems, you can use the graphical user interface to set trace options.
The IBM Tivoli Agentless Monitoring for HP-UX Operating Systems uses RAS1 tracing and generates the logs described in Table 1. The default RAS1 trace level is ERROR.
Procedure
- Open the Manage Tivoli Enterprise Monitoring Services window.
- Select Advanced > Edit Trace Parms. The Tivoli Enterprise Monitoring Server Trace Parameters window is displayed.
- Select a new trace setting in the pull-down menu in the Enter RAS1 Filters field or type a valid string.
- General error tracing. KBB_RAS1=ERROR
- Intensive error tracing. KBB_RAS1=ERROR (UNIT:kr5 ALL)
- Maximum error tracing. KBB_RAS1=ERROR (UNIT:kr5 ALL) (UNIT:kra ALL)
As this example shows, you can set multiple RAS tracing options in a single statement.
- 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 startups 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 tracing setting can generate a large amount of trace logging. Use these settings only temporarily, while you are troubleshooting problems. Otherwise, the logs can occupy excessive amounts of hard disk space.
- Click OK. You see a message reporting 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 - 60 MB for each agent that is running on a computer. For example, each database instance that you monitor can generate 45 - 60 MB of log data. 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).
Use collector trace logs as an additional source of troubleshooting information.
The KDC_DEBUG setting and the Maximum error tracing setting can generate a large amount of trace logging. Use these settings only temporarily while you are troubleshooting problems. Otherwise, the logs can occupy excessive amounts of hard disk space.
Parent topic:
RAS trace parameters