|
| 1 | +--- |
| 2 | +id: alarm_inhibit |
| 3 | +title: Alarm Inhibition |
| 4 | +sidebar_label: Alarm Inhibition |
| 5 | +keywords: [ Open Source Monitoring System, Alarm Convergence, Alarm Inhibition ] |
| 6 | +--- |
| 7 | + |
| 8 | +> Alarm inhibition is used to configure the inhibition relationship between alarms. When an alarm occurs, other alarms can be suppressed. It can be understood as "important" alarms suppressing " |
| 9 | +> unimportant" alarms. For example, the alarm generated by a server crash suppresses the alarms generated by other services on this server. |
| 10 | +
|
| 11 | +## Prerequisites |
| 12 | + |
| 13 | +- Correctly configure the alarm grouping rule |
| 14 | + |
| 15 | +## Inhibit rule configuration |
| 16 | + |
| 17 | +- Inhibit Rule Name: The name that uniquely identifies the suppression rule |
| 18 | + |
| 19 | +- Source Labels: When the alarm contains these tags, the target alarm will be suppressed. Multiple tags can be added. |
| 20 | + |
| 21 | +> Identify the tag of the "important" alarm. The alarm tag needs to contain all source tags to suppress the alarm marked by the target tag. |
| 22 | +
|
| 23 | +- Target Labels: Alarms matching these tags will be suppressed. |
| 24 | + |
| 25 | +> Identify the label of "unimportant" alarms. Alarm labels need to contain all target labels to be suppressed. |
| 26 | +
|
| 27 | +- Equal Labels: Labels for determining alarm correlation. Supports up to 10 labels. |
| 28 | +- Enabled: Enable or disable this inhibit rule |
| 29 | + |
| 30 | +## Example |
| 31 | + |
| 32 | +Scenario: Use Hertzbeat to monitor two Centos servers 192.168.1.1, 192.168.1.2, and Redis services Redis-1 and Redis-2 deployed on the two servers. |
| 33 | +And configure the following threshold rules: |
| 34 | + |
| 35 | +- Monitor Centos Linux / Monitor availability. Bind label `server-status:down` |
| 36 | +- Monitor Redis database / Monitor availability. Bind label `redis-status:down` |
| 37 | + |
| 38 | +If you need to achieve that when the Centos downtime alarm is generated, the Redis alarm will no longer be generated, you can configure the following alarm suppression rules: |
| 39 | + |
| 40 | +- Source label: `server-status:down` |
| 41 | +- Target label: `redis-status:down` |
| 42 | +- Equal label: `instancehost` |
| 43 | + |
| 44 | +When the Centos 192.168.1.1 downtime alarm is generated, the Redis-1 unavailable alarm will no longer be generated. And at the same time, when Centos 192.168.1.2 is running normally and Redis-2 is |
| 45 | +unavailable, the alarm notifying Redis-2 unavailable will be generated normally. |
0 commit comments