Agent policy for Java
Several built-in Agent Policies are provided with BMC Application Diagnostics Agent for Java:
- Light
Records the least amount of information and has a low performance hit on the recorded application. - Medium
Records more information than the Light policy, and has a higher performance hit on the recorded application. This is the out-of-the-box default policy. - Deep
Records extensive details of transactions and has a severe performance hit on the recorded application. Use this policy sparingly. - Standalone
Use the Standalone policy when BMC Application Diagnostics is not integrated with BMC Real User Experience Monitoring. The settings are the same as the Light policy, except for any settings related to BMC Real User Experience Monitoring, which improves the performance. - Max
The Max policy fully activates all recording parameters, for use in small proof-of-concept environments. The Max policy has the following characteristics:- Overrides global and custom threshold settings to maximize the number of "interesting" transactions that are considered for capture.
- Records all types of technologies
- Has a very short heartbeat interval so that Agents are updated quickly
Choosing the right policy
- Use the Standalone policy if BMC Application Diagnostics is not integrated with BMC Real User Experience Monitoring.
- Use a Light, Medium (default), or Deep policy by evaluating the configuration settings in the following table.
The table includes a selection of significant properties in the Agent Policies.
Properties that are commented out (that is, begin with a # character) have a default value that is usually mentioned in the property's comment.
Comparison of Light, Medium, and Deep policies
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*