The New Relic Agent Framework causes an application to be automatically configured to work with a bound New Relic Service.
Detection Criterion | Existence of a single bound New Relic service.
|
Tags | new-relic-agent=<version> |
Users may optionally provide their own New Relic service. A user-provided New Relic service must have a name or tag with newrelic
in it so that the New Relic Agent Framework will automatically configure the application to work with the service.
The credential payload of the service may contain the following entries:
Name | Description |
---|---|
license_key |
(Optional) Either this credential or licenseKey must be provided. If both are provided then the value for license_key will always win. The license key to use when authenticating. |
licenseKey |
(Optional) As above. |
*** |
(Optional) Any additional entries will be applied as a system property appended to -Dnewrelic.config. to allow full configuration of the agent. |
For general information on configuring the buildpack, refer to Configuration and Extension.
The framework can be configured by modifying the config/new_relic_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 New Relic repository index (details). |
version |
The version of New Relic to use. Candidate versions can be found in this listing. |
The framework can also be configured by overlaying a set of resources on the default distribution. To do this, add files to the resources/new_relic_agent
directory in the buildpack fork. For example, to override the default new_relic.yml
add your custom file to resources/new_relic_agent/newrelic.yml
.