Fix up node_md_disks changelog entry

Fixes: https://github.com/prometheus/node_exporter/issues/1759

Signed-off-by: Ben Kochie <superq@gmail.com>
This commit is contained in:
Ben Kochie 2020-06-29 16:30:59 +02:00
parent 8d436bedf5
commit 1f46669916
No known key found for this signature in database
GPG Key ID: C646B23C9E3245F1

View File

@ -21,7 +21,7 @@
* The label named `state` on `node_systemd_service_restart_total` metrics was changed to `name` to better describe the metric. #1393 * The label named `state` on `node_systemd_service_restart_total` metrics was changed to `name` to better describe the metric. #1393
* Refactoring of the mdadm collector changes several metrics * Refactoring of the mdadm collector changes several metrics
- `node_md_disks_active` is removed - `node_md_disks_active` is removed
- `node_md_disks` now has a `state` label for "fail", "spare", "active" disks. - `node_md_disks` now has a `state` label for "failed", "spare", "active" disks.
- `node_md_is_active` is replaced by `node_md_state` with a state set of "active", "inactive", "recovering", "resync". - `node_md_is_active` is replaced by `node_md_state` with a state set of "active", "inactive", "recovering", "resync".
* Additional label `mountaddr` added to NFS device metrics to distinguish mounts from the same URL, but different IP addresses. #1417 * Additional label `mountaddr` added to NFS device metrics to distinguish mounts from the same URL, but different IP addresses. #1417
* Metrics node_cpu_scaling_frequency_min_hrts and node_cpu_scaling_frequency_max_hrts of the cpufreq collector were renamed to node_cpu_scaling_frequency_min_hertz and node_cpu_scaling_frequency_max_hertz. #1510 * Metrics node_cpu_scaling_frequency_min_hrts and node_cpu_scaling_frequency_max_hrts of the cpufreq collector were renamed to node_cpu_scaling_frequency_min_hertz and node_cpu_scaling_frequency_max_hertz. #1510