Open ghost opened 7 years ago
The averages are gathered every 10 seconds and averages over the past 10 seconds, so fluctuations are expected and they will not be accurate as it is not an average over time...
I will investigate this a bit more and see if I can come up with more accurate values, problem is I have to make some sort of tes tbed to be able to compare the values to something...
I'm not getting any sent or received values with 0.5.2.20
./check_nrpe -H 10.25.14.2 -c check_network -a 'detail-syntax=Name: %(name), Sent: %(sent), Received: %(received)'
: Name: Intel(R) PRO/1000 MT Network Connection, Sent: 0, Received: 0|'Intel(R) PRO/1000 MT Network Connection_total'=0;10000;100000
Using last pre-release 0.5.1.19
check_network returns average bps values that seem quite inaccurate.
While it used to return a fixed increasing value with precedent release, it is now showing changing values more in coherence with a fluctuating network activity, but these values are not coherent to the real load.
I've been simulating outgoing traffic on the network card (Gb), reaching almost full load, but the check returns bottom-low values (from 0 to around 15 bps)
If starting some downloads, the traffic speed showed by Firefox would be around 550 - 650 ko/s, while the check returned values around 20 000 - 50 000 bps, which would make 2,5 - 6,25 ko/s (check run without any filter)
I tried to run the check with "sent" and "received" filter but couldn't figured out how to make it work (got empty output (
cli CRITICAL : :
)The NSClient++ doc about check_network (https://docs.nsclient.org/0.5.1/reference/windows/CheckSystem/#check_network) says rates are in Bytes/s and the command output says bps (quite confusing)