IBM Tivoli Composite Application Manager for Application Diagnostics, Version 22.214.171.124
Configure the Data Collection settings
Use the Data Collection settings to set and modify the system settings for the managing server to...
- regulate the frequency of data collection
- percentage of data stored
- level of monitoring
The default data collection settings can be established at the managing server level, then overridden by configuration settings specific to each configured data collector.
To configure the Data Collection settings, from the MSVE, go to...
Administration | Managing Server | System Properties
System Resources Polling Frequency How often the system resources requests information from your application server. The default setting is 60 seconds. Request Sampling Rate Percentage of requests stored in the database for reporting and analysis. The default request sampling rate is 2%. Default Monitoring Level Current default monitoring level for all servers connected to the application monitor. This is the case when configuring a server for the first time and bringing up the server under the management of the application monitor. The default monitoring level for is L2 (Problem Determination).
Level Mode Description L1 Production Provide availability management, system resources, and basic request-level data. This monitoring level has a low impact on the CPU overhead per transaction and is appropriate for servers that are not malfunctioning. L2 Problem determination Provide production level monitoring plus advanced request data, including external component and CPU information, as well as additional monitoring fields and functions. Under problem determination mode you can view component traces. These are traces that show J2EE request-related events that are made to external services. Use this level when you suspect a problem or need to capture data about external events but do not need all the method-level data. When selected, you will be given the option to check MP for Method Profiling. This feature allows you to determine how often the data collector will aggregate method data and send the data to the managing server: 1-999 minutes. You can view the method profile reports on the Method Profiling Management page. L3 Tracing Provide all available reporting elements. For example, in L3 the server activity display shows additional data for the following columns: Accumulated CPU, Last Known Class Name, Last Known Method, and Last Known action. In addition, on the Request Detail page, the method trace with SQL statements are also available. L3 has inherently higher overhead than the other monitoring levels. Use this level for servers that have been selected for diagnostics and detailed workload characterization.
Transaction CPU Time (CICS only) Whether the CPU times for a CICS transaction will be collected or not. The CPU times for CICS tasks are reported, but if you want to avoid overhead from the data capture, adjust these settings as necessary. Select one of the following four options for collecting transaction CPU:
- Do Not Collect
- Collect at Monitoring Level L1, L2, and L3
- Collect at Monitoring Level L2 and L3
- Collect at Monitoring Level L3 only
Maximum Method Records The maximum number of method trace records. The records will be cycled through, showing the 10,000 (or Maximum Method Records value) most recent methods in the system. The default value is 10,000. Maximum IMS Message Data Length The maximum length of the IMS message data. Default 256.
Parent topic:System properties
Configure the Enterprise Overview display
Configure the SNMP network