The Riverbed Appinternals Agent Framework causes an application to be bound with a Riverbed Appinternals service instance.
| Detection Criterion | Existence of a single bound Riverbed Appinternals agent service. The existence of an agent service is defined by the VCAP_SERVICES payload containing a service name, label or tag with appinternals as a substring.
|
| Tags | riverbed-appinternals-agent=<version> |
When binding Appinternals using a user-provided service, it must have appinternals as substring. The credential payload can contain the following entries:
| Name | Description |
|---|---|
rvbd_dsa_port |
(Optional)The AppInternals agent (DSA) port (default 2111). |
rvbd_agent_port |
(Optional) The AppInternals agent socket port (default 7073). |
rvbd_moniker |
(Optional) A custom name for the application (default supplied by agent process discovery). |
NOTE
Change rvbd_dsa_port and rvbd_agent_port only if there is a port conflict
cf cups spring-music-appinternals -p '{"rvbd_dsa_port":"9999","rvbd_moniker":"my_app"}'
cf bind-service spring-music spring-music-appinternals
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/riverbed_appinternals_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 Riverbed Appinternals agent repository index (details). |
version |
The version of the Riverbed Appinternals agent to use. |
NOTE
If the Riverbed Service Broker's version is greater than or equal to 10.20, the buildpack will instead download Riverbed AppInternals agent from Riverbed Service Broker and will fall back to using repository_root in config/riverbed_appinternals_agent.yml only if Service Broker failed to serve the Agent artifact.
NOTE
If the Rivered verstion is 10.21.9 or later, the buildpack will load the profiler normally, instead of from the Service Broker. This allows for creating multiple offline buildpacks containing different versions.