Monitor List¶
The Monitor List clearly displays all configured monitors and provides key information such as alert strategies, creator, updater, etc. It supports efficient monitor management through search, filtering, import, and other functions. Furthermore, you can directly jump to view the abnormal event records and operation logs triggered by the monitors, ensuring the 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; disabled monitors can be re-enabled.
-
Clone Monitor: You can directly clone the selected monitor.
-
Edit Monitor: You can edit the monitor status and rule configuration.
-
Manual Trigger Detection: Supports manually triggering monitor detection. Silent rules take 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 Events: You can view the unrecovered events triggered by this monitor and perform event management.
-
View Related Views: Can be associated with a dashboard; supports configuration during editing.
-
Delete Monitor: You can delete the monitor. Data cannot be recovered after deletion, but event data is retained.
Batch Operations¶
You can perform batch operations on monitors, including enabling, disabling, deleting, and exporting.
Additionally, you can directly configure alert strategies for monitors here and apply them to the selected monitors. The configuration of a new alert strategy will overwrite the existing alert settings of the monitor.
Tag Display¶
The system supports adding tags to monitors. You can select existing tags or manually input them; press Enter to create a new tag. Events triggered by monitor detection will also carry these tags.
Added tags are displayed directly in the list after saving. You can quickly find monitors under a specific tag using the left Quick Filter > Tags.
Tag Logic Supplement
- The tag value format is flexible; it can be
value(e.g.,host) orkey:value(e.g.,host:123). - If a custom tag
keyconflicts with other event attributes (excepttags), the custom tag will be discarded. For example, if a monitor is grouped byhost, generating an event attributehost:001, a custom taghost:000added at this time will be discarded and not written into the event attributes.
Cancel Authorization Display¶
If the current workspace has its data authorization revoked, monitors querying data using the corresponding authorization will be automatically turned off. An ! symbol will appear after the monitor name in the current monitor explorer, indicating that the current cross-workspace data authorization is invalid and requires checking for any related authorization adjustments.
SLO Linkage¶
Monitors added to an SLO as an SLI will display a special identifier:
Hover to view the list of associated SLOs; 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, management is facilitated.
Note
- When configuring alert strategies, a 2-minute waiting processing time is set for the abnormal event detection of the monitor to avoid data impact due to network or storage delays.
- Each monitor must select an alert strategy upon creation, defined by the system as "Default".
- When deleting an alert strategy, the monitors under it will be automatically categorized under "Default".
For more details, please refer to How to Create and Manage Alert Strategies.
Multiple Rules¶
For list-level operations involving multiple monitor rules, you can perform the following operations.
Filter and Search¶
Use the left Quick Filter to quickly locate target monitors based on alert strategy, status, tags, and monitor type.
You can also directly search by monitor name, monitor ID, or alert strategy name in the search box.
Import¶
Supports importing monitor configuration JSON files exported from the system. Imported monitors are automatically grouped. If "Delete and import monitors with the same name" is checked, the system will first delete existing monitors with the same name before importing.
During import:
- If monitors with the same name are found, 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.
Note
The imported JSON file must be a system configuration file.
Export All¶
Click to export the configuration of all monitor rules in the current workspace.


