sendnrw/windows_exporter
2
0
Fork 0
mirror of https://github.com/prometheus-community/windows_exporter.git synced 2026-10-21 03:59:04 +02:00
Code Issues Packages Projects Releases Wiki Activity

mixin: group alerts by collector area and add alerts for default and opt-in collectors (#2777)

Browse Source 
Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de>
This commit is contained in:
Jan-Otto Kröpke
2026-10-18 12:54:31 +02:00
committed by GitHub
parent eed518c3e1
commit d1b74b5ce3
104 changed files with 3751 additions and 302 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/runbooks/windowsnetworkdiscards.md
+14 -6
View File
@@ -4,9 +4,15 @@ title: WindowsNetworkDiscards
## Meaning
The sum of inbound and outbound discarded packet rates exceeds the configured
threshold for 15 minutes. The default is one discard per second per interface.
Discards count packets dropped without a packet error, such as buffer exhaustion.
Discarded inbound and outbound packets make up more than the configured share
of all packets on an interface for 15 minutes. The default
`networkDiscardRatioThreshold` is 1 percent. The ratio divides the discard rates
(`windows:net_received_discarded:rate` plus `windows:net_outbound_discarded:rate`)
by the packet rates (`windows:net_received_packets:rate` plus
`windows:net_sent_packets:rate`). Discards count packets dropped without a packet
error, such as buffer exhaustion. Interfaces that carry no packets produce no
sample and cannot alert. The alert keeps firing for `keepFiringFor` after the
ratio drops below the threshold.
## Impact
@@ -17,7 +23,8 @@ timeouts. Some drops may be expected under a deliberate traffic policy.
1. Inspect `windows:net_received_discarded:rate` and
`windows:net_outbound_discarded:rate` to identify the direction and affected
`nic`.
`nic`, and compare them with the packet rate recordings to see whether a low
packet rate inflates the ratio.
2. Compare traffic, directional utilization ratios, and
`windows_net_output_queue_length_packets` with the normal baseline.
3. Inspect `Get-NetAdapterStatistics`, switch-port drops, adapter buffers,
@@ -30,5 +37,6 @@ timeouts. Some drops may be expected under a deliberate traffic policy.
Relieve congestion, distribute traffic, or add bandwidth. Correct buffer, driver,
or virtual switch problems when evidence identifies them. Review intentional
drop policies with the network owner before changing thresholds. Confirm discard
rates and application retransmissions return to the expected baseline.
drop policies with the network owner before raising
`networkDiscardRatioThreshold`. Confirm discard rates and application
retransmissions return to the expected baseline.