Python Agent Settings

You can configure operating settings for the Python Agent using a configuration file or by setting environment variables in the application environment. This page lists the Python Agent settings. 

See Configure the Agent for information about the configuration file.

Older version of the environment variables are backward compatible and are deprecated which will eventually be removed in future releases. You will have to update the environment variables to the latest version.
The new environment variables take precedence over the deprecated variables in case both are set in an environment (eg. APPDYNAMICS_AGENT_APPLICATION_NAME takes precedence over the deprecated APPD_APP_NAME if both are set).

[agent]

[agent:proxy]

[wsgi]

If both the script and module directives are specified, the module directive takes precedence.

The module value may be the fully-qualified name of a module, or it may be the fully-qualified name of a module followed by a colon and the name of the WSGI callable in that module. In the latter form, the module directive overrides the callable directive.

Both the long-form of the module directive and the callable directive may take either the name of a symbol, or the name of a symbol followed by an empty pair of parentheses. In the latter form, the callable is taken to be the result of calling the callable specified by the directive. This latter form can be used with Django; for example:

module = django.core.handlers.wsgi:WSGIHandler()

[log]

[controller]

This section specifies configuration for the AppDynamics Controller.

Directive	Description	Example	Default	Environment Variable
host	Controller host	mycontroller.example.org	Required	APPDYNAMICS_CONTROLLER_HOST_NAME
port	Controller port	9000	8090 for HTTP on-prem 443 for HTTPS, in which case SSL must also be set	APPDYNAMICS_CONTROLLER_PORT
ssl	Is SSL set be used to talk to the controller? on or off	on	off	APPDYNAMICS_CONTROLLER_SSL_ENABLED
account	AppDynamics Controller account	user1	For a single-tenant controller defaults to customer1. Otherwise required.	APPDYNAMICS_AGENT_ACCOUNT_NAME
accesskey	AppDynamics Controller account access key	XC6v2n8m2$543	Required. To find your account name and access key, click in the upper right corner of the AppDynamics UI, then click License.	APPDYNAMICS_AGENT_ACCOUNT_ACCESS_KEY
certfile	Controller Certificate This certfile must be the default agent keystore (found under site-packages/appdynamics_proxysupport/lib/security/cacerts) with necessary additional .pem/.crt certs embedded within it using keytool. Java proxy supports only .jks and .pkcs12 formats in the keystore. If you want to include .crt format in Java proxy, run the following command: keytool -import -alias rootCA -file /etc/ssl/certs/ca-certificates.crt -keystore cacerts.jks -storepass changeit	/tmp/ssl/cacerts	Optional	APPDYNAMICS_CONTROLLER_SSL_CERTFILE

[controller:http-proxy]

If you need to use an HTTP proxy to talk to your Controller, use this section to configure the HTTP proxy.

[proxy]

If PROXY_DEBUG_PORT is defined, then -agentlib:jdwp=transport=dt_socket,server=y,suspend=${START_SUSPENDED},address=${PROXY_DEBUG_PORT}  is used as the debug opt. PROXY_DEBUG_PORT takes priority over DEBUG_OPT if both are specified. Also ensure that PROXY_DEBUG_PORT is not set if you want to use a self defined DEBUG_OPT. 

[eum]

[services:snapshot]

[services:transaction-monitor]

[services:analytics]

Directive	Description	Example	Default	Environment Variable
host	Analytics Agent host	analytics-agent.example.org	localhost	APPDYNAMICS_ANALYTICS_HOSTNAME
port	Analytics Agent port	9000	9090	APPDYNAMICS_ANALYTICS_PORT
ssl	Set it on to enable SSL communication with the Analytics Agent	on	off	APPDYNAMICS_ANALYTICS_SSL_ENABLED
ca-file	Certificate of the CA authority that signed the certificate of Analytics Agent. The certificate format must be .pem If there are intermediate certificate authorities, specify the path of the chain of trust in place of the root certificate authority.	/tmp/certs/ca-cert.pem	optional	APPDYNAMICS_ANALYTICS_CAFILE