diff options
author | Sachi King <nakato@nakato.io> | 2019-02-10 21:00:04 +1100 |
---|---|---|
committer | Ben Kochie <superq@gmail.com> | 2019-02-10 11:00:04 +0100 |
commit | 18fc512fc4d50c2463fa4de8845d33c04a0ed529 (patch) | |
tree | f67aa27f91e5313289545728dbaff57e1ca2e0d0 /CHANGELOG.md | |
parent | e0d6d1185988bb1eb33779539399dd0e6cab0238 (diff) | |
download | prometheus_node_collector-18fc512fc4d50c2463fa4de8845d33c04a0ed529.tar.bz2 prometheus_node_collector-18fc512fc4d50c2463fa4de8845d33c04a0ed529.tar.xz prometheus_node_collector-18fc512fc4d50c2463fa4de8845d33c04a0ed529.zip |
Bond: Monitor bond mii_status not link operstate (#1124)
With a bond interface the state of the slave interface from the bond's
point of view is reflected in `mii_status` and is independent of the
link's `operstate`.
When a bond is monitored with `miimon`, `mii_status` will reflect the
state of the physical link as configured via the operator.
When a bond is monitored via `arp_interval` the `mii_status` will
reflect the results of the bond ARP checking. This means the link can
be down from the bond's point of view, but up from a physical
connection point of view.
If a bond is not monitored via miimon or arp, the `mii_status` should
likely be always `up`, however I have observed a case where this is not
true and the `operstate` is `up` while `mii_status` is `down`. Kernel
bond documentation stresses that a bond should not be configured without
one of `mii_mon` or `arp_interval` configured however.
This change results in the metric 'node_bonding_active' matching the
up/down state of the bond's point of view rather than operstate.
Signed-off-by: Sachi King <nakato@nakato.io>
Diffstat (limited to 'CHANGELOG.md')
-rw-r--r-- | CHANGELOG.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md index 77f84cb..6d6abb2 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md | |||
@@ -6,6 +6,7 @@ | |||
6 | other network metrics #1224 | 6 | other network metrics #1224 |
7 | * The cpufreq metrics now separate the `cpufreq` and `scaling` data based on what the driver provides. #1248 | 7 | * The cpufreq metrics now separate the `cpufreq` and `scaling` data based on what the driver provides. #1248 |
8 | * The labels for the network_up metric have changed, see issue #1236 | 8 | * The labels for the network_up metric have changed, see issue #1236 |
9 | * Bonding collector now uses `mii_status` instead of `operstatus` #1124 | ||
9 | 10 | ||
10 | ### Changes | 11 | ### Changes |
11 | 12 | ||
@@ -21,6 +22,7 @@ | |||
21 | * [FEATURE] Add kstat-based Solaris metrics for boottime, cpu and zfs collectors #1197 | 22 | * [FEATURE] Add kstat-based Solaris metrics for boottime, cpu and zfs collectors #1197 |
22 | * [FEATURE] Add uname collector for FreeBSD #1239 | 23 | * [FEATURE] Add uname collector for FreeBSD #1239 |
23 | * [FEATURE] Add diskstats collector for OpenBSD #1250 | 24 | * [FEATURE] Add diskstats collector for OpenBSD #1250 |
25 | * [CHANGE] Bonding state uses mii_status #1124 | ||
24 | 26 | ||
25 | ## 0.17.0 / 2018-11-30 | 27 | ## 0.17.0 / 2018-11-30 |
26 | 28 | ||