Severity Definitions¶
Severity is used to indicate the severity and priority of an incident, affecting filtering and sorting in the incident list, as well as matching on-call escalation strategies. The system provides default severities and supports customizing severities according to your team's needs.
Default Severities¶
The system has 4 built-in default severities:
| Field | Description |
|---|---|
| P0 | Default severity configuration. Critical business functions are unavailable and affect a large number of users. |
| P1 | Default severity configuration. Critical business functions are unavailable, but the impact on users is limited, e.g., only affecting internal users. |
| P2 | Default severity configuration. Non-critical business functions are unavailable. Persistent failure will significantly impact user experience. |
| Unknown | Default severity configuration. Business impact is unknown. |
Custom Severities¶
In addition to the default severities, you can configure custom severities (up to 10 can be added) to meet your various needs.
Add Severity¶
- Click Add Severity.
- Select a severity color block.
- Enter the severity name and its description.
- Confirm.
Manage Severities¶
For severities, you can perform the following operations:
-
Edit: Click the edit button to modify the color, name, and description of the current custom severity.
-
Delete: Click to delete the current severity.
Enable/Disable Default Configuration¶
-
Enable: If the default configuration is enabled and there are newly added custom severities in the current workspace, both default and custom severities can be selected when creating or modifying an incident.
-
Disable: If the default configuration is disabled, you can only select custom severity configurations when creating/modifying an incident.
- Custom severities must already exist to ensure there are selectable severities when creating/modifying an incident.
- In cases where an anomaly event is generated by a monitor or Intelligent Inspection and synchronized to create an incident, the incident severity will be set to empty.
- If incidents using default severities still exist within the workspace, their severity will be set to empty.
Impact of Platform-Level Severity Configuration¶
In addition to workspace-level severity configuration, the system also supports unified management of incident severities at the platform level (i.e., the Deployment Plan admin console). Platform-level configuration overrides workspace-level configuration:
- The system supports managing incident severity configuration at the platform level. After enabling the global configuration, the workspace-level incident severity configurations configured here will no longer apply.
- After global severities are enabled, if other severity configurations are applied in rules such as monitors or Intelligent Inspection within the workspace, the severity of newly generated incidents will be set to empty.