Create an alert policy
Describes how to create an alert policy in the KSV web console.
This topic describes how to create an alert policy in the KubeSphere Virtualization (KSV) web console.
Prerequisites
The alerting feature is enabled. For information about how to enable alerting, see Enable and disable alerting.
The user that you use has been granted the permissions to manage alerts. Only user admin, project administrators, and operators can manage alerts. Project viewers can view only alerts in the projects to which they belong.
Procedure
Log in to the KSV web console.
In the top navigation bar, click O&M Tools to go to the management page of O&M tools.
In the left-side navigation pane, click Alerts.
On the Alert Policies tab, click Create in the upper-right corner.
In the dialog box that appears, configure basic information for the alert policy.
Parameter Description NameThe custom name of the alert policy.The name can contain only lowercase letters, digits, and hyphens (-), and must start and end with a lowercase letter or a digit. The name can contain up to 16 characters in length.AliasThe alias of the alert policy.The alias can contain any characters and be up to 16 characters in length.Duration (mins)The duration of the alert.An alert is fired if the duration has been reached.SeverityThe severity of the alert. Valid values:- Critical: an alert condition that requires immediate response.
- Major: an error without the need to take immediate action.
- Minor: a non-critical condition that has not caused a degradation in performance.
DescriptionThe description of the alert policy.The description can be up to 128 characters in length. The character types are unlimited.Click Next and configure the alert rule for the policy.
Parameter Description Target TypeThe type of targets for monitoring. KSV can monitor nodes and VMs.Alert RuleThe alert rule of the alert policy. The supported alert rules vary based on the target type.- For nodes, you can configure a rule based on the following metrics: CPU usage, available memory, memory usage, available local disk size, local disk size, local disk reads, local disk writes, disk read throughput, and disk write throughput.
- For VMs, you can configure a rule based on the following metrics: CPU usage, memory usage, local disk reads, local disk writes, outbound rate, and inbound rate.
Monitoring TargetThe name of the node or VM for monitoring. You can monitor one or more targets.Click OK. The alert policy appears in the alert policy list after it is created.