health: fix alarm line options syntax in the docs (#10974)
Ilya Mashchenko committed
Apr 14, 2021 at 16:40 UTC
545e2a551fff63f0a7695371f7e2d093af59a18e
1 file changed
+4
-4
health/REFERENCE.md
+4
-4
@@ -72,7 +72,7 @@ Netdata parses the following lines. Beneath the table is an in-depth explanation
72
| [`exec`](#alarm-line-exec) | no | The script to execute when the alarm changes status. |
73
| [`delay`](#alarm-line-delay) | no | Optional hysteresis settings to prevent floods of notifications. |
74
| [`repeat`](#alarm-line-repeat) | no | The interval for sending notifications when an alarm is in WARNING or CRITICAL mode. |
75
-| [`option`](#alarm-line-option) | no | Add an option to not clear alarms. |
75
+| [`options`](#alarm-line-options) | no | Add an option to not clear alarms. |
76
| [`host labels`](#alarm-line-host-labels) | no | List of labels present on a host. |
77
78
The `alarm` or `template` line must be the first line of any entity.
@@ -386,12 +386,12 @@ repeat: [off] [warning DURATION] [critical DURATION]
386
- `critical DURATION`: Defines the interval when the alarm is in CRITICAL state. Use `0s` to turn off the repeating
387
notification for CRITICAL mode.
388
389
-#### Alarm line `option`
389
+#### Alarm line `options`
390
391
-The only possible value for the `option` line is
391
+The only possible value for the `options` line is
392
393
```yaml
394
-option: no-clear-notification
394
+options: no-clear-notification
395
```
396
397
For some alarms we need compare two time-frames, to detect anomalies. For example, `health.d/httpcheck.conf` has an