Monitor List¶
The monitor list clearly displays all configured monitors and provides key information such as alert strategies, creator, and updater. 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 monitor, ensuring transparency and traceability of the monitor's 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 Test: Supports manual triggering of monitor detection, mute rules take effect, and an event is generated and alerts are sent after triggering.
- 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 Incident Management.
- View Related Views: You can associate dashboards, which can be configured during editing.
- You can delete the monitor, and the data cannot be recovered after deletion, but the event data is retained.
Batch Operations¶
You can perform batch enable, disable, delete, and export operations on monitors.
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 them, and press Enter to create new tags. Events triggered by monitor detection will also be tagged with these tags.
The added tags can be directly displayed in the list after saving. You can quickly find the monitors under the corresponding tags based on the Quick Filter > Tags on the left.
Tag Logic Supplement
- The tag value format is not limited, it can be
value
(such ashost
), orkey:value
(such ashost:123
). - If the custom tag
key
duplicates other event attributes (excepttags
), the custom tag will be discarded. For example, if the monitor is grouped byhost
, generating the event attributehost:001
, the custom taghost:000
added at this time will be discarded and will not be written into the event attributes.
Unauthorized Display¶
If the current workspace is canceled Data Authorization, monitors that query using the corresponding data will be automatically closed, and the monitor name in the current monitor explorer will be followed by !
, 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 special identifiers:
Hover to view the associated SLO list, 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 abnormal event detection of the monitor will set a 2-minute waiting processing time to avoid data impact due to 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 be automatically classified as "default".
For more details, refer to How to Create and Manage Alert Strategies.
Multiple Rules¶
For list-level multiple rules of monitors, 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 the monitor configuration JSON file exported by the system, and automatically groups after importing. 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 there are monitors with the same name, you can choose to delete the existing monitors with the same name.
Note
The imported JSON file must be from the system configuration file.
Export All¶
After clicking, you can export all monitor rule configurations in the current workspace.