APMPlus now supports reporting via a third-party probe. With a probe from Bonree, monitoring data can be sent to the APMPlus server for application performance monitoring. This topic introduces how to use a third-party probe from Bonree to report monitoring data to APMPlus.

Usage disclaimer

The third-party probe introduced in this topic is provided and maintained by Bonree. APMPlus does not guarantee their availability or reliability. For probe-related issues, please contact Bonree directly (Feishu technical support group).

Prerequisites

Download the third-party probe and extract it to the installation directory. The download URL is as follows:

Architecture	Download URL
AMD64	https://one.bonree.com/agent/down/Bonree-SmartAgent-Linux-Serverless-volcano-cloud-9.7.0.tar.gz
ARM	https://one.bonree.com/agent/down/Bonree-SmartAgent-Linux-ARM-Serverless-volcano-cloud-9.7.0.tar.gz

After downloading, extract the archive (e.g., Bonree-SmartAgent-Linux-Serverless-volcano-cloud-9.7.0-alpha1.tar.gz) into the probe directory and ensure the file structure is organized as follows.

Procedure

Currently supported reporting languages include Java, Python, Go, and PHP.

Java application monitoring deployment

Python application monitoring deployment

Go application monitoring deployment

PHP application monitoring deployment

Use Java process parameters to attach the probe and its configuration to the application, as shown in the example below:

tip

The Otel configuration items are consistent with OpenTelemetry, but currently only the items shown in the example below are supported.

The Otel protocol currently supports only the HTTP protocol.

Otel.traces.sampler only supports the ParentBased effect and does not support probability sampling for individual spans.

The value of Otel.traces.sampler.arg is in parts per thousand.

Otel.exporter.otlp.endpoint distinguishes between public and private networks. For private network deployment, use http://apmplus-cn-{region}.ivolces.com/server_collect/apmplus_open_telemetry/{appkey}.

Variable	Description
{Installation directory}	The installation directory. Configure according to your actual environment.
{region}	The region where data is reported to the APMPlus server. Select according to your actual deployment. For currently supported region IDs, see Available regions.
{appkey}	For the method to obtain the APMPlus authentication credential, see How to obtain the APMPlus AppKey.
{path/to/you/app.jar}	The path of the application to be monitored. Configure according to your actual environment.

Modify the agentloader.yml configuration to enable the probe.

Load the probe via environment variables, as shown in the example below:

Parameter	Description
LD_PRELOAD	The agent loader path, through which the probe can be injected automatically into the application process. The {Installation directory} represents the actual installation directory. For AMD64 architecture, use {Installation directory}/lib/libagentloader-amd64-linux.so For ARM architecture, use {Installation directory}/lib/libagentloader-aarch64-linux.so.
BR_DEPLOYMENT_METADATA	Enable serverless mode.
OTEL_SERVICE_NAME	The service name of the application.
OTEL_EXPORTER_OTLP_ENDPOINT	Data reporting endpoint. For public network deployment, use https://apmplus-{region}.volces.com/server_collect/apmplus_open_telemetry/{appkey}. For private network deployment, use http://apmplus-{region}.ivolces.com/server_collect/apmplus_open_telemetry/{appkey}. The following variables must be replaced according to your actual environment. {region}: The region where data is reported to the APMPIus server. Select according to your actual deployment. For currently supported region IDs, see Available regions. {appkey}: The authentication credential for APMPlus. To obtain it, see How to obtain the APMPlus AppKey.

Modify the agentloader.yml configuration to enable the probe.

Load the probe via environment variables, as shown in the example below:

Parameter	Description
LD_PRELOAD	The agent loader path, through which the probe can be injected automatically into the application process. The {Installation directory} represents the actual installation directory. For AMD64 architecture, use {Installation directory}/lib/libagentloader-amd64-linux.so For ARM architecture, use {Installation directory}/lib/libagentloader-aarch64-linux.so.
BR_DEPLOYMENT_METADATA	Enable serverless mode.
OTEL_SERVICE_NAME	The service name of the application.
OTEL_EXPORTER_OTLP_ENDPOINT	Data reporting endpoint. For public network deployment, use https://apmplus-{region}.volces.com/server_collect/apmplus_open_telemetry/{appkey}. For private network deployment, use http://apmplus-{region}.ivolces.com/server_collect/apmplus_open_telemetry/{appkey}. The following variables must be replaced according to your actual environment. {region}: The region where data is reported to the APMPIus server. Select according to your actual deployment. For currently supported region IDs, see Available regions. {appkey}: The authentication credential for APMPlus. To obtain it, see How to obtain the APMPlus AppKey.

Modify the agentloader.yml configuration to enable the probe.

Load the probe via environment variables, as shown in the example below:

Parameter	Description
LD_PRELOAD	The agent loader path, through which the probe can be injected automatically into the application process. The {Installation directory} represents the actual installation directory. For AMD64 architecture, use {Installation directory}/lib/libagentloader-amd64-linux.so For ARM architecture, use {Installation directory}/lib/libagentloader-aarch64-linux.so.
BR_DEPLOYMENT_METADATA	Enable serverless mode.
OTEL_SERVICE_NAME	The service name of the application.
OTEL_EXPORTER_OTLP_ENDPOINT	Data reporting endpoint. For public network deployment, use https://apmplus-{region}.volces.com/server_collect/apmplus_open_telemetry/{appkey}. For private network deployment, use http://apmplus-{region}.ivolces.com/server_collect/apmplus_open_telemetry/{appkey}. The following variables must be replaced according to your actual environment. {region}: The region where data is reported to the APMPIus server. Select according to your actual deployment. For currently supported region IDs, see Available regions. {appkey}: The authentication credential for APMPlus. To obtain it, see How to obtain the APMPlus AppKey.

Application Performance Management Plus