Modifying an App Visibility agent policy file to collect and monitor application information

This section presents parameters that you can modify in an App Visibility policy.

Before you begin

To perform this procedure, you must have Application Administrator-level access.

To edit a policy file

1. From the navigation pane, select Administration > App Visibility Agent Policies.

2. On the App Visibility Agent Policies page, click the action menu of the policy that you want to edit, and select Edit.

   Tip

   You cannot edit an out-of-the-box policy (displayed with a lock icon ), but you can create a copy of the policy and edit the copy:

   1. From the action menu of the policy that you want to copy, select Save As.
   2. On the Create App Visibility Agent Policy File page, rename the policy and modify it according to your requirements.

3. On the Edit App Visibility Agent Policy page, modify the policy according to your requirements.

   Policy editing rules

   BMC recommends that you contact Customer Support when modifying the settings for the first time, to ensure that your modifications do not impact the system adversely. When you change the policy settings, adhere to the following rules:

   • Each line in the policy file has only one property, in a property=value format.
   • Do not change property names; you can only change values.
   • White spaces are ignored except within the value string (that is, between the first non-blank character after the "=" delimiter and the last non-blank character in the line).
   • Both Windows and Linux line feed markers are supported.
   • Hash marks (#) at the beginning of a line signify comments.
   • Property values can only be ASCII characters within the range of 0-127.
4. Click Save.
5. (Optional)  Apply the policy to relevant agents or set it as a default policy. For details, see Managing App Visibility policy files.

The following topics describe some of the most common configuration settings:

• Comparing default App Visibility agent policies for Java
• Concealing sensitive data recorded by the App Visibility agents
• Reducing the number of similar requests
• Adjusting the percentage of sampled requests: Agent overhead
• Collecting data for stack traces that exceeded thresholds
• Persisting tagged transactions
• Disabling end-user monitoring in App Visibility
• Monitoring standalone services for .NET Framework
• Following up on problematic transactions: escalation