Monitor List¶

The monitor list clearly displays all configured monitors and provides key information such as alert strategies, creators, and updaters. It supports efficient management of monitors through search, filtering, and import functions. Additionally, you can directly jump to view the incident records and operation logs triggered by the monitors, ensuring transparency and traceability of monitor status and behavior.

Single Rule¶

For a single monitor rule, you can perform the following operations:

Enable/Disable: You can enable or disable the monitor. New monitors are enabled by default and can be re-enabled after being disabled.
Clone Monitor: You can directly clone the selected monitor.
Edit Monitor: You can edit the monitor status and rule configuration.
Manual Trigger Detection: Supports manual triggering of monitor detection, with mute rules taking effect. After triggering, an event is generated and an alert is sent.
Operation Audit: You can view the operation records related to the monitor.
View Related Incidents: You can view the unresolved incidents triggered by this monitor and perform Incident Management.
View Related Views: You can associate dashboards, which can be configured during editing.
Delete Monitor: You can delete the monitor. After deletion, the data cannot be recovered, but the incident data is retained.

Batch Operations¶

You can perform batch operations on monitors such as enabling, disabling, deleting, and exporting.

Additionally, you can directly configure alert strategies for monitors here, applying them to the selected monitors. New alert strategy configurations will overwrite the existing alert settings of the monitors.

Tag Display¶

The system supports adding tags to monitors. You can select existing tags or manually input new ones, which will be created after pressing Enter. The incidents triggered by the monitor detection will also carry these tags.

The added tags will be displayed directly in the list after saving. You can quickly find the monitors under the corresponding tags by using the Quick Filter > Tags on the left.

Tag Logic Supplement

The tag value format is not limited. It can be value (e.g., host) or key:value (e.g., host:123).
If a custom tag key conflicts with other incident attributes (except tags), the custom tag will be discarded. For example, if a monitor is grouped by host, generating an incident attribute host:001, a custom tag host:000 added at this time will be discarded and not written into the incident attributes.

Unauthorized Display¶

If the current workspace is unauthorized for data, monitors that query using the corresponding data will be automatically closed. In the current monitor explorer, a ! symbol will appear after the monitor name, indicating that the current cross-workspace data authorization is invalid, and you need to check if there are any adjustments to the related authorization.

SLO Linkage¶

Monitors added to SLO as SLI will display a special identifier:

Hover to view the associated SLO list, and click to open the SLO details page.

Alert Strategies¶

The alert strategy function supports creating meaningful monitor combinations when setting up monitors. By filtering corresponding monitors through alert strategies, it facilitates management.

Note

When configuring alert strategies, the incident detection of monitors will set a 2-minute waiting time to avoid data being affected by network or storage delays.
Each monitor must select an alert strategy when created, which is defined as "default" by the system.
When deleting an alert strategy, the monitors under it will automatically be classified as "default".

For more details, refer to How to Create and Manage Alert Strategies.

Multiple Rules¶

For list-level multiple monitor rules, you can perform the following operations.

Filter Search¶

In the Quick Filter on the left, you can quickly locate target monitors based on alert strategies, status, tags, and monitor types.

You can also directly enter the monitor name, monitor ID, or alert strategy name in the search box to search.

Import¶

Supports importing monitor configuration JSON files exported by the system. After import, they are automatically grouped. If "Delete and import monitors with the same name" is checked, the system will first delete monitors with the same name and then import.

During the import process:

If monitors with the same name appear, you can choose to delete the existing monitors with the same name.
If some monitors involve cross-space monitoring and the current space has not obtained authorization from the target space, these monitors will fail to import.