You need to enable JavaScript to run this app.
Application Performance Management Plus

Application Performance Management Plus

  • Documentation
    • Application Performance Management PlusUser guideServer monitoringIntegration guideIntegrating applications via VKE
Copy page
Download PDF
Integration guide
Integrating applications via VKE
Copy page
Download PDF
Integrating applications via VKE
Server-side Monitoring has integrated with VKE, providing end-to-end, full-trace performance monitoring for applications deployed in VKE clusters. This topic describes how to deploy an application in a VKE cluster and integrate the application with Server-side Monitoring.​
Prerequisites​
  • The apmplus-opentelemetry-collector add-on has been installed in the VKE cluster. For details, see Installing the add-on.​
Limits​
Workspaces have independent data reporting credentials. To use workspaces for data management and data isolation, ensure that the apmplus-opentelemetry-collector add-on has been upgraded to v3.1.0 or later.​
Procedure​
tip​
‌When creating a workload‌ of any type (Deployment, StatefulSet, Job, CronJob, and DaemonSet), you can enable Server-side Monitoring‌ for the workload. This topic uses the Deployment creation as an example. For information about how to configure a workload of a different type, see Workloads.​
Method 1: Use the console​
  1. Log in to the VKE console. ​
  1. In the left navigation pane, select Cluster. In the cluster list, click the target cluster name to go to the cluster management page.​
  1. In the left navigation pane, select Workload > Deployment.​
  1. Click Create Deployment. In the Container configuration step, check End-to-end Application Performance Management and configure monitoring parameters.​
  • The key parameters in this feature scenario are as follows. For instructions on configuring other parameters, see Creating Deployments.​
  • ​
    Parameter​
    Description​
    Monitor application type​
    Specify the type of application to monitor. Currently supported types include Java, Python, and Node.js.​
    Server-side Monitoring workspace​
    Select the workspace to which the service belongs. The workspace is used for data management and data isolation. For more details, see Managing workspaces.​
    Monitor Service Name​
    (Optional) Configure a name for the monitoring service. This name will be used as the name of the monitoring task for the workload and displayed in the service list in the Server-side Monitoring console. The name helps you easily distinguish between different monitoring tasks.​
    tip​
    If this name is not specified, the system will use the workload name as the monitoring service name.​
    ​
  1. After configuring other parameters, click Confirm.​
Method 2: Use kubectl​
tip​
Before creating a Deployment via the kubectl tool, ensure that the following conditions are met:​
  • kubectl has been used to connect to the target cluster. For detailed instructions, see Connecting to clusters.​
When you create a workload in the cluster using YAML, you can configure the application performance observability feature via annotations. The sample YAML code for different workload types varies slightly.​
​
Java
Python
NodeJS
​
The sample configuration for Java applications is as follows:​
​
apiVersion: apps/v1​
kind: Deployment​
metadata:​
name: deployment-demo # The Deployment name.​
namespace: default # The owning namespace of the Deployment.​
spec: ​
replicas: 1 # The Deployment replica count.​
selector: ​
matchLabels: ​
app: nginx​
template: ​
metadata: ​
labels: ​
app: nginx​
annotations:​
instrumentation.apmplus.volcengine.com/inject-java: "true" # Enable APMPlus observability injection.​
instrumentation.apmplus.volcengine.com/workspace: default # Specify the workspace to which the service belongs.​
instrumentation.apmplus.volcengine.com/java-container-names: "nginx,myapp" # (Optional) Specify containers to which injection applies.​
apmplus.volcengine.com/service.name: "doc-pod-demo" # (Optional) Specify a name for the service corresponding to the workload in APMPlus. If it is not configured, the Pod name is used as the server name by default.​
spec:​
containers:​
- name: nginx # The container name.​
image: cr-cn-beijing.volces.com/demo-namespace/demo-repo:v1 # The container image address and tag.​
ports:​
- containerPort: 80 # The container port number.​
env: # Use an environment variable to define the service name of the container in APMPlus. This configuration takes precedence over the apmplus.volcengine.com/service.name annotation.​
- name: OTEL_SERVICE_NAME​
value: "container-demo"​
​
​
​
If your workload has containerized applications in different languages, you can inject annotations for these applications simultaneously. Example:​
​
template: ​
metadata: ​
labels: ​
app: nginx​
annotations:​
instrumentation.apmplus.volcengine.com/workspace: default # Specify the workspace to which the service belongs.​
instrumentation.apmplus.volcengine.com/inject-java: "true" # Enable observability injection for the Java application.​
instrumentation.apmplus.volcengine.com/java-container-names: "myapp" # Specify the container named myapp to implement Java injection.​
instrumentation.apmplus.volcengine.com/inject-python: "true" # Enable observability injection for the Python application.​
instrumentation.apmplus.volcengine.com/python-container-names: "myapp2" # Specify the container named myapp2 to implement Python injection.​
spec:​
...​
​
Validate results​
  1. Log in to the Server-side Monitoring console. ​
  1. Click the Click to go to service list link to access the server-side monitoring page.​
  1. In the left-side navigation pane of server-side monitoring, click Service Monitoring > Service List. In the service list, you can view the name of the monitoring service for the workload in the cluster.​
  1. Click the service name to view the detailed monitoring information. For details, see Service monitoring.​
​
Last updated: 2026.09.20 10:55:53