AppDynamics Application Intelligence Platform

3.8.x Documentation

PDFs

Videos

Release Notes

Skip to end of metadata
Go to start of metadata

These properties support communication between the PHP proxy component and the Controller.

Where to Configure App Agent Properties

You can configure the PHP proxy properties in the controller-info.xml file in the <php_agent_install>/proxy/conf directory.
You can also set most of these properties on the command-line when you install the agent. See Install the App Agent for PHP.

The installer generates a new controller-info-xml file every time it runs. You can edit controller-info-xml to add, delete or modify the proxy configuration properties, but be aware that your changes are overwritten every time you re-install the agent, so if you reinstall the agent you need to update controller-info-xml manually.

The only properties that cannot be added on the install command-line are Enable Orchestration Property and Force Agent Registration Property.

Example PHP Proxy controller-info.xml File

<?xml version="1.0" encoding="UTF-8"?>
<controller-info>

	<controller-host>192.168.1.20</controller-host>

	<controller-port>8090</controller-port>

	<controller-ssl-enabled>false</controller-ssl-enabled>

	<application-name>Magento</application-name>

	<tier-name>php</tier-name>

	<node-name>php0</node-name>

	<controller-ssl-enabled>true</controller-ssl-enabled>

	<enable-orchestration>false</enable-orchestration>

</controller-info>

Proxy Properties

This section describes the proxy configuration properties.

Proxy-Controller Communication Properties

Controller Host Property

Description: This is the host name or the IP address of the AppDynamics Controller. Example values are 192.168.1.22 or myhost or myhost.abc.com. This is the same host that you use to access the AppDynamics browser-based user interface. For an on-premise Controller, use the value for application server host name that was configured when the Controller was installed.

Set when invoking the agent installer.

Element in controller-info.xml:  <controller-host>

Type: String

Default: None

Required: Yes

Controller Port Property

Description: This is the HTTP(S) port of the AppDynamics Controller. This is the same port that you use to access the AppDynamics browser-based user interface.

If the Controller SSL Enabled property is set to true, specify the HTTPS port of the Controller; otherwise specify the HTTP port. See Controller SSL Enabled Property.

Set when invoking the agent installer.

Element in controller-info.xml:  <controller-port>

Type: Positive Integer

Default: For on-premise installations, port 8090 for HTTP and port 8181 for HTTPS are the defaults.

Required: Yes

Proxy Identification Properties

Application Name Property

Description:  This is the name of the logical business application that the instrumented node belongs to.
If a business application of the configured name does not exist, it is created automatically.

Set when invoking the agent installer.

Element in controller-info.xml: <application-name>

Type: String

Default: None

Required: Yes

Tier Name Property

Description:  This is the name of the logical tier that this node belongs to.

Set when invoking the agent installer.

Element in controller-info.xml: <tier-name>

Type: String

Default: None

Required: Yes

Node Name Property

Description: This is the name of the instrumented node.
In general, the node name must be unique within the business application and physical host.

Set when invoking the agent installer.

Element in controller-info.xml:  <node-name>

Type: String

Default: None

Required: Yes

Mulit-Tenant Mode Properties

Description:  If the AppDynamics Controller is running in multi-tenant mode or if you are using the AppDynamics SaaS Controller, specify the account name and account access key for this agent to use to authenticate with the Controller. If you are using the AppDynamics SaaS Controller, the Welcome email sent by AppDynamics provides this information.

If the Controller is running in single-tenant mode (the default) there is no need to configure these values.

Account Name Property

Description: This is the account name used to authenticate with the Controller.

Can be set when invoking the agent installer.

Element in controller-info.xml:  <account-name>

Type: String

Default: None

Required: Yes for AppDynamics SaaS Controller and other multi-tenant users; no for single-tenant users.

Account Access Key Property

Description: This is the account access key used to authenticate with the Controller.

Can be set when invoking the agent installer.

Element in controller-info.xml: <account-access-key>

Type: String

Default: None

Required: Yes for AppDynamics SaaS Controller and other multi-tenant users; no for single-tenant users.

Other Properties

Controller SSL Enabled Property

Description:  When set to true, this property specifies that the agent should use SSL (HTTPS) to connect to the Controller. If SSL Enabled is true, set the Controller Port property to the HTTPs port of the Controller. See Controller Port Property.

Element in controller-info.xml:  <controller-ssl-enabled>

Type: Boolean

Default: False

Required: No

Enable Orchestration Property

Description:  When set to true, enables auto-detection of the controller host and port when the app server is a compute cloud instance created by an AppDynamics orchestration workflow. See Controller Host Property and Controller Port Property.

In a cloud compute environment, auto-detection is necessary for the Create Machine tasks in the workflow to run correctly.

If the host machine on which this agent resides is not created through AppDynamics workflow orchestration, this property should be set to false.

Element in controller-info.xml:  <enable-orchestration>

Type: Boolean

Default: False

Force Agent Registration Property

Description:  Set to true only under the following conditions:

  • The Agent has been moved to a new application and/or tier from the UI
    and
  • You want to override that move by specifying a new application name and/or tier name in the agent configuration.

Element in controller-info.xml: <force-agent-registration>

Type: Boolean

Default: False

Required: No

Learn More