For multiple Apache web server instances that share the same Apache Agent, ensure that Comm dirs, set using AppdynamicsProxyCommDir directive, for each proxy process is different. Also ensure that the node names in each server configuration file, appdynamics_agent.conf, are also different.

• LoadFile: Loads the Splunk AppDynamicsAgent SDK shared library. Assuming the agent is installed in /opt, the setting would be/opt/appdynamics-sdk-native/sdk_lib/lib/libappdynamics_native_sdk.so. Make sure to set this parameter for Alpine and Linux. This parameter is not applicable to AIX environments.

  For example:

  LoadFile /opt/appdynamics-sdk-native/sdk_lib/lib/libzmq.so.5
  LoadFile /opt/appdynamics-sdk-native/sdk_lib/lib/libappdynamics_native_sdk.so

  libappdynamics_native_sdk.so has a runtime dependency on libzmq and libuuid. These libraries can be found in the same directory as ibappdynamics_native_sdk.so.

• LoadModule: Loads the Splunk AppDynamics Apache Agent shared library. The correct module is libmod_appdynamics.so for Apache 2.4 and libmod_appdynamics22.so for Apache 2.2. Required.

  Note: OHS and IHS 7.x - 8.x require the Apache 2.2 module. IHS 9.x uses the Apache 2.4 module. To run Apache agent on AIX, you must have Apache 2.4 as the minimum version.

  Apache 2.4 example:

  LoadModule appdynamics_module /opt/appdynamics-sdk-native/WebServerAgent/Apache/libmod_appdynamics.so

  Apache 2.2 example:

  LoadModule appdynamics_module /opt/appdynamics-sdk-native/WebServerAgent/Apache/libmod_appdynamics22.so

• AppDynamicsEnabled: Must be included and set to ON for web server monitoring to be enabled. Otherwise, monitoring is disabled by default.

  For example:

  AppDynamicsEnabled ON

  To disable monitoring, set to OFF or remove the Splunk AppDynamics module include statement (see Configure the Apache Server for AppDynamics) from the Apache configuration file.

• AppDynamicsControllerHost: Hostname or IP address of the controller to connect to. Required.

  For example:

  AppDynamicsControllerHost mycontroller.saas.appdynamics.com

• AppDynamicsControllerPort: Controller HTTP(S) port. For SaaS, use 443 for HTTPS or 80 for HTTP. For on-premises, HTTP defaults to 8090 and HTTPS defaults to 8181. Optional. Configure if you do not want to use these defaults. If you are using HTTPS, the SSL setting (AppDynamicsControllerSSL) must also be set.

  For example:

  AppDynamicsControllerPort 80

• AppDynamicsControllerSSL: Set to connect to the Controller over SSL. Default is OFF. Set to ON to enable SSL connection and also set the AppDynamicsControllerPort to an HTTPS port.

  For example:

  AppDynamicsControllerSSL OFF

• AppDynamicsAccountName: Splunk AppDynamics account name. For on-premises controllers, find your credentials under > License in the Controller. For SaaS Controllers, Splunk AppDynamics provides your credentials in your Welcome email. Required.

  For example:

  AppDynamicsAccountName MyCompany

• AppDynamicsAccessKey: Splunk AppDynamics account access key. For on-premises Controllers, find your credentials under License in the Controller. For SaaS Controllers, Splunk AppDynamics provides your credentials in your Welcome email. Required.

  For example:

  AppDynamicsAccessKey zd8yjh5yuy5k

• AppDynamicsProxyHost: Proxy server hostname or IP address. Optional. Use if the agent connects to the Controller through a HTTP proxy server.
• AppDynamicsProxyport : Proxy server port. Optional. Use if the agent connects to the Controller through a HTTP proxy server.

• AppDynamicsApplication: Splunk AppDynamics application name. See Overview of Application Monitoring. Required.

  For example:

  AppDynamicsApplication MyWS2App

• AppDynamicsTier: Splunk AppDynamics tier name. See Overview of Application Monitoring. Required.

  For example:

  AppDynamicsTier MyWS2

• AppDynamicsNode: Splunk AppDynamics node name. See Overview of Application Monitoring. The node name is required and each node name must be unique.

  For example:

  AppDynamicsNode WS2_1

• AppDynamicsTlsProtocol: It is the TLS version that the agent utilizes to communicate with the Controller. The default value is TLS 1.2. You can specify TLS 1.3. Any input other than TLS 1.3 is ignored and the default value is considered.

  For example:

  AppDynamicsTlsProtocol TLSv1.3

• AppDynamicsCustomTags : User-defined custom tags as a set of key-value pair. You can use these custom tags in the Controller. These tags are applicable to the nodes. You can define multiple key-values pairs separated by a comma.

  For example:

  AppDynamicsCustomTags CustomTagName=value1,CustomTagName2=value2

#Load the Splunk AppDynamics SDK.
LoadFile /opt/appdynamics-sdk-native/sdk_lib/lib/libzmq.so.5
LoadFile /opt/appdynamics-sdk-native/sdk_lib/lib/libappdynamics_native_sdk.so
#Load the Apache Agent. In this example for Apache 2.4
LoadModule appdynamics_module /opt/appdynamics-sdk-native/WebServerAgent/Apache/libmod_appdynamics.so
AppDynamicsEnabled On
#Splunk AppDynamics Controller connection.
AppDynamicsControllerHost mycontroller.saas.appdynamics.com
AppDynamicsControllerPort 80
AppDynamicsControllerSSL OFF
#Account credentials
AppDynamicsAccountName MyCompany
AppDynamicsAccessKey zd8yjh5yuy5k
#Configure Controller connection through an HTTP proxy server.
#AppDynamicsProxyHost <proxy host>
#AppDynamicsProxyPort <proxy port>
#Business application, tier, node
AppDynamicsApplication MyApache2App
AppDynamicsTier Apache2
AppDynamicsNode Apache2_1