Several built-in agent policies are provided with the App Visibility agent for Java:
Records the least amount of information and has a low performance hit on the recorded application.
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.
Records extensive details of transactions and has a severe performance hit on the recorded application. Use this policy sparingly.
Use the Standalone policy when App Visibility is not integrated with Real End User Experience Monitoring Software Edition. The settings are the same as the Light policy, except for any settings related to the integration.
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
- Uses a very short heartbeat interval so that agents are updated quickly
Choosing the right policy
- Use the Standalone policy if App Visibility is not integrated with BMC Real End User Experience Monitoring Software Edition.
- 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
Data recording and collection configurations
Percentage of total requests that are sampled by the agent
Valid values: 0-100
Time frame (in milliseconds) in which only the worst SLA breaching request is persisted
Time frame (in milliseconds) in which error requests are buffered
Number of different error types that can be sent in a specified time
List of parameters (such as HTTP parameters and headers) with values that might contain sensitive information that should be masked. Parameters are case insensitive.
Default = password, j_password, pass, pswd, authorization, passwordInput, j_id_id3:passwordInput, passwd, vpasswd
For details, see Concealing sensitive data recorded by the App Visibility agents.
Enables global modifiers to be added to each recording rule
JDBC snapin to collect extended query data
JMS snapin to collect extended data
Servlet snapin to collect extended data
- false = Only the client user name, user IP, user browser, URL, method, request and response lengths are collected
- true = All request parameter and header names and values are collected
Maximum extended data size
Longer data is truncated.
Maximum number of back-to-back, same-method calls before ignoring further calls
Maximum number of method calls in a server request before ignoring further calls
Determines the level of impact in terms of possible agent overhead: 1 is the lowest impact and 5 is the highest. Increased impact can provide more accurate and comprehensive results.
- 1 = brief
- 2 = light
- 3 = medium
- 4 = heavy
- 5 = verbose
To configure recording rules, contact Customer Support.