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()

Tags are key-value pairs that are associated with your entities, such as applications, tiers, nodes, and so on. These tags act as metadata that help you find your application resources in the Controller UI. You can reduce the Mean Time To Detection (MTTD) of any entity related issues by tagging them using appropriate custom tags. To know how to import tags in Controller, see Custom Tag APIs.

You can define the custom tags during the configuration of Python Agent, see Configure the Agent. These tags are sent to the Controller UI and help filter data using tag-based filtering and tag-based columns. If you make changes to your tagging configuration, you must restart the agent.

For example:

[tags]
tag1 = value1
tag2 = value2
tag3 = value3

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 Note: 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

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

Reuse Node Name

To reuse node names in AppDynamics, you have to set nodereuse property to true. When you set this property to true, you do not have to supply a node name, but you do need to provide a node name prefix using nodereuseprefix .

This property is useful for monitoring environments where there are many VMs (Virtual Machines) with short life spans. When set to true, AppDynamics reuses the node names of historical VMs for new VMs. This avoids a proliferation of differently named nodes in AppDynamics over time, particularly when the nodes are essentially identical processes that run over different times.

AppDynamics generates a node name with App, Tier, and Sequence number, and the node names are pooled. For example, the sequence numbers are reused when the nodes are purged (based on the node lifetime).

System Property: nodereuse

Type: Boolean

Default: False

Required: No

Reuse Node Name Prefix

When you configure the agent to reuse node names, use this property to specify the prefix that the Controller uses to generate node names dynamically.

System Property: nodereuseprefix

Type: String

Default: None

Required: When nodereuse=true

Backend resolution is the association of a backend (through identity) to node or tier.