You may need to set the following optional directives unless instructed by support:

• AppDynamicsBackendNameSegments: The number of URL segments that are displayed in the backend naming. This is only applicable for requests routing through the mod_proxy, when Apache is acting as a reverse proxy server, also-known-as a gateway server. Specify the rule configuration for backend naming in the appdynamics_agent.conf file. The default value is 0 and only the IP address of the request URL is displayed. If you set a value of 2, then the first two segments along-with the IP address are displayed. Therefore for a request proxying to http://1.1.1.1/services/admin/abc, the backend is named as http://1.1.1.1/services/admin.

  For example:

  AppDynamicsBackendNameSegments 2

• AppDynamicsResolveBackends: Controls the way Apache module backends appear in the Controller UI. If ON, metrics for Apache modules are shown as part of downstream tiers or backends. Module backends do not appear on flow maps. If OFF, Apache module backends appear in the flow maps with their own metrics. See Apache Modules. Defaults to ON. Optional.

  For example:

  AppDynamicsResolveBackends OFF

• AppDynamicsTraceAsError: If ON, tracepoints are written as errors to the Apache logs, by default error_log. Default is OFF. Optional.

  AppDynamicsTraceAsError OFF

• AppDynamicsReportAllInstrumentedModules: If OFF , the agent reports only modules that occur during the HANDLER stage of Apache request processing. If ON, the agent reports modules during all stages of Apache request processing. The default is OFF .

  For example:

  AppDynamicsReportAllInstrumentedModules OFF

• AppDynamicsLaunchProxy: If ON, the agent launches the proxy automatically when on startup. If OFF, you need to manually launch the proxy. If your system uses any command to do a graceful restart of Apache, such as log rotate, or if your system encounters heavy loads, you should set this property to OFF. The default is OFF.

  AppDynamicsLaunchProxy OFF

  For information about how to examine and resolve proxy issues that may prevent an application agent from connecting to the Controller, see Dynamic Language Agent Proxy.

  You may want to launch the proxy manually for debugging. For example, to set a different proxy root directory or runtime directory or to output additional debugging information.

• AppDynamicsProxyJreDir: Specify the JRE path.

  Warning: This parameter applies only to the AIX platform. This parameter becomes mandatory if AppDynamicsLaunchProxy is enabled. However, the JRE path gets discarded if AppDynamicsLaunchProxy is disabled, in this case, you must launch the proxy manually. See Launch the Proxy.

• AppDynamicsRequestCacheCleanupInterval: Timeout in milliseconds after which the request cache is cleaned up by Java proxy. Proxy consists of a queue that takes all the requests from the agents and stores these requests for processing. Sometimes, this message queue can have an enormous cache within an interval of a minute under high load scenarios. Therefore as a preventive measure, a cleanup timer with a default value of 60 secs is available. To monitor long transactions, increase the cleanup interval, but you must be vigilant of the high cache or memory usage.

  For example:

  AppDynamicsRequestCacheCleanupInterval 120000

  Note: If you are running the proxy manually, then while running the launch proxy command add the following flag:

  --req-cache-cleanup-interval=120000

• AppDynamicsProxyCommDir- Path to the directory containing the domain control socket, which the agent uses to start a Splunk AppDynamics node. Defaults to <agent_install_directory>/logs/appd-sdk. If you modify this setting, make sure that the directory path does not exceed 107 characters, which is the Linux limit to the socket file name size. If the directory path is too long, you will get an error message when the agent attempts to start.

  AppDynamicsProxyCommDir <agent_install_directory>/proxy/altcommdir

• For Filtering sensitive-data and privileged information, see Filter Sensitive Data.