-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Net plugin bytes sent/recieved resets to 0 if host reboots #4531
Comments
It’s the OS that resets the counter. Use non negative difference or non negative derivative for calculations. Sent with GitHawk |
@voiprodrigo Can you explain what you mean by a non-negative derivative to avoid something like this. Do you have an example? I've been struggling to figure this out for weeks, and have not been able to find an answer.... I'm pretty desperate at this point. I'm not using a derivative for this item Example of what happens when it sets to 0 in the middle of a time range: Query:
|
Add a last() to bytes_recv within non_negative_difference() and group by time. The larger the time value, the less resolution you'll see in the lines. Suit to taste. |
Bug? Maybe feature request?
On freebsd.
Current behavior:
Collecting Net data
bytes_sent
andbytes_recv
go sup over time, as expected. However when the host reboots these are set to 0 and go up again as data is sent/recieved.Desired behavior:
The
bytes_sent
andbytes_recv
maintain their previous values and continue to go up.Use case:
When this reset to 0 is completely breaks any total bandwidth usage queries as it relies on the first vs last
bytes_sent
andbytes_recv
for the timerange to get a total.Ie. start: 100 bytes, end: 4000 bytes. Total for range is 3900 bytes. If it was to reset to 0 in the middle of a daterange you get negative bandwith usage using this.
The text was updated successfully, but these errors were encountered: