Skip to content

Latest commit

 

History

History
44 lines (36 loc) · 2.64 KB

framework-app_dynamics_agent.md

File metadata and controls

44 lines (36 loc) · 2.64 KB

AppDynamics Agent Framework

The AppDynamics Agent Framework causes an application to be automatically configured to work with a bound AppDynamics Service.

Detection CriterionExistence of a single bound AppDynamics service. The existence of an AppDynamics service defined by the VCAP_SERVICES payload containing a service name, label or tag with app-dynamics as a substring.
Tagsapp-dynamics-agent=<version>
Tags are printed to standard output by the buildpack detect script

User-Provided Service

When binding AppDynamics using a user-provided service, it must have name or tag with app-dynamics in it. The credential payload can contain the following entries:

Name Description
account-access-key (Optional) The account access key to use when authenticating with the controller
account-name (Optional) The account name to use when authenticating with the controller
host-name The controller host name
port (Optional) The controller port
ssl-enabled (Optional) Whether or not to use an SSL connection to the controller

Configuration

For general information on configuring the buildpack, refer to Configuration and Extension.

The framework can be configured by modifying the config/app_dynamics_agent.yml file in the buildpack fork. The framework uses the Repository utility support and so it supports the version syntax defined there.

Name Description
repository_root The URL of the AppDynamics repository index (details).
version The version of AppDynamics to use. Candidate versions can be found in this listing.

Additional Resources

The framework can also be configured by overlaying a set of resources on the default distribution. To do this, add files to the resources/app_dynamics_agent directory in the buildpack fork. For example, to override the default app-agent-config.xml add your custom file to resources/app_dynamics_agent/conf/app-agent-config.xml.