Docs

Observability Platform

VMP alert configuration

Creating VMP alert rules

You can configure alert rules by using PromQL statements, use Alert Center to monitor specific metrics in a specified workspace, and configure alerts based on metric thresholds. This topic describes how to manually configure an alerting rule by using a PromQL statement.

Prerequisites

An alert notification policy has been created to specify the recipients, notification templates, and other information for receiving notification messages. For details, see Creating notification policies.

An alert aggregation policy has been created to aggregate alert notifications and prevent alert storms. For details, see Creating aggregation policies.

Limits

Each account can create up to 500 alert rules.

You can configure up to 100 labels and 100 annotations for an alert rule.

Procedure

Method 1: Create an alert rule

Method 2: Import or export alert rules via JSON

You can create an alert rule from scratch in the console and configure key parameters such as the query statement and the trigger policy in sequence. This method applies to scenarios that require customization or that involve a small number of alert rules.

In the left navigation pane, click Alert Center > Alert Configuration to go to the Alert Configuration management page.

In the Alert Configuration section on the left, select VMP and click the Alert Rule tab.

Click Create alert rule and configure the relevant parameters for the VMP alert rule as needed. After completion, click Confirm.

Category	Parameter	Description
Basic information	Name	Specify a name for the alert rule as a unique identifier. Duplicate names are not allowed.
		Project	Projects are a platform-provided resource management mechanism that allows you to group resources for different business applications or projects. Project-based authorization with Identity and Access Management (IAM) facilitates resource isolation and data security, as well as cost calculation across cloud resources. For details, see Project management. tip By default, VMP alert rules are added to the default project, and the project cannot be changed.
		Tags	A tag is a key-value pair that allows you to classify and aggregate cloud resources from different dimensions. You can use tags for resource authorization and bill splitting. For details, see Managing labels. tip You can add up to 50 tags to a single alert rule.
Alert trigger configuration	workspace	The workspace that you want to monitor and trigger alerts. The workspace of Volcengine Managed Service for Prometheus (VMP) is an abstract integration of data and collection rules, which provides users with standard cloud Prometheus capabilities. For more details, see Workspace overview.
		Query statement	Use standard PromQL statements to configure monitoring objects or metrics.
		Metric preview	Visually preview the metrics that match the query statement. By default, data from the last hour is queried.
		Trigger policy	Configure an alert trigger policy. You can specify the alert level, condition, threshold, and condition duration. Alert level: Select P0, P1, or P2 to set different alert levels. If you do not select an option, alerts at this level are not configured. Comparison condition: Specify the comparison condition between the PromQL statement and the threshold. You can configure multiple comparison conditions. Valid values: Greater than, Greater than or equal to, Less than, Less than or equal to, Equal to, and Not equal to. Threshold: Set the threshold of the metric. Condition duration: Configures the duration for which the metric meets the condition. Valid values: Trigger immediately: An alert is triggered immediately when the alert condition is met. Custom duration: Select an alert trigger time. For example, 1 minute means that the alert will be triggered after the alert condition has been met for 1 minute.
Alert notification	Notification policy	Select an alert notification policy. The system sends alerts to the specified contacts based on the alert levels and contact groups configured in the notification policy. For notification policy details, see Creating notification policies.
Alert notification		Aggregation policies	Select an alert aggregation policy. An aggregation policy is primarily used to configure the aggregation cycle for alerts. It groups a batch of alerts for notification, preventing a large number of alert messages from being generated in a short period when alerts are triggered frequently. For details, see Creating aggregation policies.
Advanced configuration	Label	Configure the labels of the alert rule. Labels are primarily used for alert identification, grouping, deduplication, and route matching. A label consists of a key and a value. Key: The key is a string. It can start with a letter or an underscore (_), but cannot start with a double underscore (__). Allows 1–256 characters, which can contain letters, digits, and underscores (_). Value: The value is a string. It can contain Chinese characters, letters, digits, and special characters and must be 1 to 512 characters in length. tip When you configure multiple types of labels, the priorities of the labels are sorted in the following descending order: rule label > global label > PromQL label. Common configuration example: labels: severity: critical # Alert level business: pay # Business line alert_type: resource # Alert type
Advanced configuration		Annotation	Configure the annotations for the alert rule. Annotations are primarily used to display key information. An annotation consists of a key and a value. Valid values: Key: The key is a string. It can start with a letter or an underscore (_), but cannot start with a double underscore (__). Allows 1–256 characters, which can contain letters, digits, and underscores (_). Value: The value is a string. It can contain Chinese characters, letters, digits, and special characters and must be 1 to 512 characters in length. Common configuration example: annotations: summary: "High CPU usage on instance {{ $labels.instance }}" description: "Current CPU usage is {{ $value \| humanizePercentage }}, threshold is 80%" runbook_url: "https://xxx/docs/cpu-alert" dashboard_url: "https://grafana/xxx"

Export VMP alert rules from another workspace as a JSON file, and then import them into the VMP alert rules in the current workspace. This method applies when you need to copy alert rules in batches across accounts, regions, projects, or workspaces.

tip

The import and export features enable quick synchronization of alert configurations across accounts, regions, projects, or workspaces for efficient reuse. For VMP alert rules, the synchronization granularity is at the workspace level.

In the left navigation pane, click Alert Center > Alert Configuration to go to the Alert Configuration management page.

In the Alert Configuration section on the left, select VMP and click the Alert Rule tab.

In the upper-right corner, click the button, select Actions, and perform the corresponding operation. Use the import/export feature to import VMP alert rules that are exported from another workspace into the current workspace.

Actions	Description
Export selected VMP rules	Export the rules that are selected in the VMP alert rule list to a local JSON file. tip Only items on the current page can be selected. Cross‑page selection is not supported. Do not arbitrarily modify the structure of the JSON file, because it may cause import failures. If you do not have the required technical knowledge, we recommend that you do not edit the JSON file directly.
Export all VMP alert rules that meet search criteria	Export all VMP alert rules that meet the filter criteria to a local JSON file. The export is not affected by pagination. You can filter data by region, project, workspace, alert rule group, or search function.
Import a JSON file to generate VMP alert rules	Use JSON files to import VMP alert rules exported from other accounts, regions, projects, or workspaces into the current VMP alert rule module. During the import, you can configure the target region, project, workspace, and name suffix. warning Only rules of the same type can be imported. For example, you can export VMP alert rules from the Beijing region and import them into the Shanghai region for use. However, VMP alert rules cannot be imported into the alert rule module for Cloud Monitor.

Last updated: 2026.09.07 19:40:07