Skip to main content
If the alert engine (monitedge) goes down, alert rules cannot execute, which has a significant impact. The engine disconnection alert feature sends timely notifications when the engine goes down, ensuring the reliability of your monitoring system. Menu Entry: Data ingestion → Edge engines → Engine Disconnection Alert
For an engine cluster composed of multiple instances, as long as at least one instance in the cluster is alive, the disconnection alert will not trigger. It only triggers when all instances in the cluster are disconnected.

Alert rule list

The list shows the configured rules and their main parameters (see Create an alert rule for what each means). You can search by keyword, customize the displayed columns, and enable or disable a rule with its switch. The page size, and which columns are shown and in what order, are remembered in the browser and reused the next time you open this list.

Create an alert rule

Click the New button to configure the following parameters in the side drawer:
1

Basic information

2

Severity

Select the severity level for alert events:
  • Critical: Urgent, typically used for core engines
  • Warning: Warning level, the default
  • Info: Informational level
3

Include and exclude rules

Include pattern and exclude pattern cannot both be empty.
4

Trigger conditions

5

Channel

Select the channel where alert events should be delivered. Alert events are processed through Flashduty On-call channels for subsequent notification dispatch and handling.

Edit and delete

Click Edit or Delete in the list to modify or delete a rule. Only the rule creator, the owner account, or admin roles can edit or delete rules.