diff options
| author | Joel Hans <joel@netdata.cloud> | 2019-12-03 07:34:15 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-12-03 07:34:15 -0700 |
| commit | e5478fac6c84081686fcfae1d9766a964ea5068f (patch) | |
| tree | 58fa0534fbf0e993b7ba2de8336f7e983063488d /collectors/proc.plugin | |
| parent | 6bb56ae15d2f3bca1b05115a736fff0ecb9d0a30 (diff) | |
Health: Proposed restructuring of health documentation (#7329)
* Squashed commits for PR
* Addressing comments from Chris and Thiago
* Changed sidebar title
* Fixes for Vlad
Diffstat (limited to 'collectors/proc.plugin')
| -rw-r--r-- | collectors/proc.plugin/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/collectors/proc.plugin/README.md b/collectors/proc.plugin/README.md index b81dd82f1b..0091e359a7 100644 --- a/collectors/proc.plugin/README.md +++ b/collectors/proc.plugin/README.md @@ -300,7 +300,7 @@ By default Netdata will enable monitoring metrics only when they are not zero. I There are several alarms defined in `health.d/net.conf`. -The tricky ones are `inbound packets dropped` and `inbound packets dropped ratio`. They have quite a strict policy so that they warn users about possible issues. These alarms can be annoying for some network configurations. It is especially true for some bonding configurations if an interface is a slave or a bonding interface itself. If it is expected to have a certain number of drops on an interface for a certain network configuration, a separate alarm with different triggering thresholds can be created or the existing one can be disabled for this specific interface. It can be done with the help of the [families](../../health/#alarm-line-families) line in the alarm configuration. For example, if you want to disable the `inbound packets dropped` alarm for `eth0`, set `families: !eth0 *` in the alarm definition for `template: inbound_packets_dropped`. +The tricky ones are `inbound packets dropped` and `inbound packets dropped ratio`. They have quite a strict policy so that they warn users about possible issues. These alarms can be annoying for some network configurations. It is especially true for some bonding configurations if an interface is a slave or a bonding interface itself. If it is expected to have a certain number of drops on an interface for a certain network configuration, a separate alarm with different triggering thresholds can be created or the existing one can be disabled for this specific interface. It can be done with the help of the [families](../../health/REFERENCE.md#alarm-line-families) line in the alarm configuration. For example, if you want to disable the `inbound packets dropped` alarm for `eth0`, set `families: !eth0 *` in the alarm definition for `template: inbound_packets_dropped`. #### configuration |