You need to enable JavaScript to run this app.
Volcengine Kubernetes Engine

Volcengine Kubernetes Engine

Copy page
Download PDF
Basic observation
Enabling observability
Copy page
Download PDF
Enabling observability
Cloud-native basic observability provides fully managed, high-performance, and highly stable cluster observability and alerting services. This topic introduces common concepts in basic observability and how to enable the cloud-native basic observability feature.​
Background​
Metric scope​
In VKE clusters, the metric scope for cloud-native basic observability is divided into three tiers: basic, standard, and full metrics. This tiered design helps you make reasonable tradeoffs between observability scope, usage cost, and troubleshooting depth. The scope of the three tiers expands progressively, enabling you to select the observability level genuinely needed at the current stage, based on cluster scale, business complexity, and operational goals. This approach prevents initial over-provisioning or observability insufficiency.​
​
Metric scope​
Description​
Basic​
Basic metrics of the monitored object. They provide insights into the basic status of the object and resource usage. This option is suitable for initial observability setup or scenarios where the focus is on core operational health.​
Standard​
[Recommended] Basic and important metrics of the monitored object. The combination of basic and important metrics provides a more comprehensive view of the object's status. This option is suitable for scenarios that require routine inspection, stability analysis, and regular issue identification.​
Full​
Basic, important, and advanced metrics of the monitored object. This tier includes all metrics of the monitored object. This option is suitable for scenarios that require high observability, in-depth analysis, and complex troubleshooting based on comprehensive data.​
​
tip​
The billing method and cost vary based on the observability metric scope and the VMP workspace's storage duration. For details, see Pay-as-you-go.​
Collectors​
Cloud-native basic observability is implemented on the VMP service and uses the prometheus-agent add-on as the collector in clusters. The add-on collects and monitors metrics for cluster infrastructure resources, control-plane components, and custom applications. When you install the prometheus-agent in your cluster, the system automatically deploys core add-ons (such as vmagent, vmoperator, kube-state-metrics, and node-exporter) and related custom resources (such as ServiceMonitor and PodMonitor). For details about the add-on, see prometheus-agent.​
Common operations​
Enable basic observability​
​
Enable for existing clusters
Enable when creating clusters
​
To enable basic observability in an existing cluster, follow the steps below:​
  1. Log in to the VKE console.​
  1. In the left navigation pane, click Cluster. Click the target cluster name to go to the management page of this cluster.​
  1. Bind a VMP workspace.​
  1. In the left navigation pane, click Operation and maintenance configuration. In the Container observability configuration section, click the Configure now link.​
  1. In the pop-up dialog box, select a VMP workspace to be bound to the cluster.​
  1. Install the collector add-on.​
  1. In the left navigation bar, click Addons.​
  1. Click the Monitoring tab. Find the prometheus-agent add-on, hover over the add-on card, and click Deploy. For add-on configuration instructions, see prometheus-agent.​
  1. Enable basic observability.​
  1. In the left navigation pane, click Cloud native observability > Overview to enter the service activation page.​
  1. Click Activate basic observability to enable cloud-native basic observability.​
  1. (Optional) Configure observability enhancement. This option allows you to enable observability for major cluster add-ons (such as core-dns and vpc-cn) with a click. You can also enable observability for individual add-ons as needed. For details, see Basic observability.​
  1. (Optional) Configure network and application observability. This feature monitors the network performance of workloads and the application performance of each interface, and generates a topology without modifying the application. Additionally, it can further trace interface calls with response errors or excessively long response times. For details, see Enabling full-stack observability.​
​
Modify the metric scope​
warning​
Modifying the metric scope will change the number of metrics collected in your cluster. Expanding the metric scope will incur additional costs. For details, see Pay-as-you-go billing.​
  1. In the left navigation bar of the cluster management page, click Observability settings.​
  1. In the upper-right corner of the configuration page, click Modify the default metric scope.​
  1. In the pop-up window, select the desired metric scope and check the Instant effective for installed add-ons option.​
  1. Click Confirm.​
Change workspaces​
  1. In the left navigation pane of the cluster management page, click Operation and maintenance configuration.​
  1. In the Container observability configuration section, to the right of the Prometheus workspace field, click ​​ to change the workspace.​
  1. In the pop-up window, select the desired workspace and check the I have been informed and agreed that the Prometheus workspace of the alert rule group will be revised and updated together option.​
  1. Click Confirm.​
Viewing observability configuration​
After enabling cloud-native basic observability, click cloud-native observability > Overview in the left navigation pane. Then, select the Observability overview tab to view the cluster observability overview.​
  • Observability settings overview: Displays the VMP workspace bound to the cluster and collector status.​
  • Basic observability overview: Displays the proportion of add-ons with basic observability enabled in the cluster and the metric tier.​
  • ​
    Parameter​
    Description​
    Enabled add-ons​
    Displays the number of add-ons that have observability enabled in the cluster and the total number of add-ons that support observability.​
    Default metric tier​
    Displays the metric scope for cluster observability. You can click ​​ to modify the observability metric scope.​
    Percentage of enabled basic metrics​
    The ratio of enabled basic metrics to all basic metrics for add-ons that have observability enabled. You can click Go to settings to select or deselect metrics for the target add-on. For details, see Basic observability.​
    Percentage of enabled non-basic metrics​
    The ratio of enabled non-basic metrics to all non-basic metrics for add-ons for which observability is enabled. You can click Go to settings to select or deselect metrics for the target add-on. For details, see Basic observability.​
    Enhanced observability​
    The status of the observability enhancement feature. You can click ​​ to enable or disable observability for major cluster add-ons, such as core-dns and vpc-cni. You can also enable observability for individual add-ons as needed. For details, see Basic observability.​
    tip​
    A green add-on mark in the console, for example, ​​, indicates that the add-on is installed in the cluster.​
    ​
  • Full-stack observability overview: Displays the status of the full-stack observability feature. Click Enable to configure the full-stack observability feature. For details, see Enabling full-stack observability.​
Viewing cluster overview​
After you enable cloud-native basic observability, you can view the cluster monitoring overview, including node status and workload performance overview.​
Node​
The node section provides node status and resource usage for all nodes in the cluster.​
  • Node status: Displays cluster node statistics, including the total number of nodes in each of the following states: Ready, Not Ready, Disk pressure, Memory pressure, PID pressure, and Network unavailable.​
  • Resource usage: Displays the top 5 list of all nodes in the current cluster for metrics such as the CPU utilization, memory utilization, inbound network traffic, outbound network traffic, disk utilization, disk I/O saturation, file descriptor saturation, and inode saturation.​
  1. In the left navigation pane of the cluster management page, select Cloud native observability > Overview. Then, select the Monitoring overview tab.​
  1. In the Node section, view cluster node information.​
Application performance overview​
The application performance overview provides performance information for all workloads in the cluster, such as the error rates and response time (P90).​
  1. In the left navigation pane of the cluster management page, select Cloud native observability > Overview. Then, select the Monitoring overview tab.​
  1. In the Workload performance overview section, view the workload performance information.​
Last updated: 2026.07.24 10:53:28