It is recommended that you create a Unix System Service that automatically starts the proxy at system startup.
Under special circumstances, you may need to set the optional directives below. Do not set these directives unless instructed by AppDynamics support.
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" on Install the Apache Agent...
Defaults to ON. Optional.
AppDynamicsTraceAsError: If ON, trace points are written as errors to the Apache logs, by default error_log. Default is OFF. Optional.
- 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.
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.
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.
AppDynamicsProxyCommDir: Path to the directory containing the domain control socket, which the agent uses to start an 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.