The Takipi Agent Framework causes an application to be automatically configured to work with OverOps Service.
| Detection Criterion | Existence of a single bound Takipi service. The existence of an Takipi service defined by the VCAP_SERVICES payload containing a service name, label or tag with app-dynamics or takipi as a substring.
|
| Tags | takipi-agent=<version> |
When binding Takipi using a user-provided service, it must have name or tag with takipi in it.
The credential payload can contain the following entries.
| Name | Description |
|---|---|
secret_key |
(Optional) The agent installation key |
collector_host |
(Optional) The remote collector hostname or IP |
collector_port |
(Optional) the remote collector port |
Setting secret_key will run a local collector alongside the agent. Setting collector_host will use a remote collector. More information can be found in OverOps Remote Collector
For general information on configuring the buildpack, including how to specify configuration values through environment variables, refer to Configuration and Extension.
The framework can be configured by modifying the config/takipi_agent.yml file. The framework uses the Repository utility support and so it supports the version syntax defined there.
| Name | Description |
|---|---|
node_name_prefix |
Node name prefix, will be concatenated with - and instance index |
application_name |
Override the Cloudfoundry default application name |
Currently, you can get the Takipi agent logs using cf files command:
cf files app_name app/.java-buildpack/takipi_agent/log/
If your container is running out of memory and exited with status 137, then you should setup and use a remote collector as explained in the User-Provided Service above section.