Docs

Application Performance Management Plus

Best practices

Isolating production and test data

If you use a root account to manage both production and test data, you can follow the steps below to isolate them, making it easier to distinguish monitoring metric changes between production and test data.

Considerations

Only services integrated via OpenTelemetry support isolating production and test data.

Only services using automatic data collection methods support isolating production and test data.

Integrate services via OpenTelemetry

OpenTelemetry is a CNCF observability project that aims to provide a standard solution. It addresses the standardization of data models, collection, processing, and export, offering vendor-agnostic services.

If your application has already integrated the OpenTelemetry SDK, the APMPlus server can receive data reported via OpenTelemetry. After integrating with APMPlus, you will gain capabilities such as RED metric generation, multi-dimensional trace search, single trace search, and topology generation.

Limits

APMPlus uses Prometheus as the storage backend for OpenTelemetry metrics and supports PromQL queries. For specific applications, see Custom dashboards and Alert management.

There are certain limitations when converting OpenTelemetry metrics to Prometheus metrics:

Same as open source, ExponentialHistogram is not supported.

Data with delta aggregation is not supported. Do not modify the default aggregation configuration on the SDK side. Ensure that the aggregation method on the SDK side is set to cumulative.

Distinguish by annotation

Log in to the VKE console, go to the Addons page, and ensure that the apmplus-opentelemetry-collector add-on has been upgraded to version 2.0.2 or later. For details, see Upgrading add-ons, Add-on update log.

Add the specified annotation to the service's Kubernetes deployment configuration to distinguish data by annotation.

Annotation	Description
instrumentation.apmplus.volcengine.com/inject-java	It is used to determine whether to enable automatic javaagent injection. true: enabled. false: disabled.
apmplus.volcengine.com/env	Inject user-defined environment information. When querying the service list on the APMPlus platform later, you can switch based on the user-specified env.
apmplus.volcengine.com/service.name	It is used to specify the service name of the current service. When manually configuring, we recommend including env characteristics. The system requires that service names be unique and does not allow the same service name to be associated with different envs.

Sample code:

apiVersion: apps/v1
kind: Deployment
metadata:
name: simple-java
labels:
app: simple-java
spec:
replicas: 1
selector:
matchLabels:
app: simple-java
template:
metadata:
labels:
app: simple-java
annotations:
instrumentation.apmplus.volcengine.com/inject-java: 'true'
apmplus.volcengine.com/env: 'test'
apmplus.volcengine.com/service.name: 'simple-java-test'
spec:
containers:
- name: simple-java
image: java_demo_simple
imagePullPolicy: Always
env:
- name: CONTAINER_RUNTIME
value: "k8s"

Restart the application.

Verify data

View service list

Select an available region.

In the service list, select env to check whether the integrated services can be found under the selected envs.

View service topology

Select an available region.

In the upper-left corner, select Service monitoring > Service topology.

On the "Service topology" page, select env to check whether the topology under the selected env is correct.

Last updated: 2026.08.12 17:18:58