Skip to content
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

95th percentile counted wrong #4318

Closed
twindh opened this issue Sep 2, 2016 · 6 comments
Closed

95th percentile counted wrong #4318

twindh opened this issue Sep 2, 2016 · 6 comments

Comments

@twindh
Copy link

twindh commented Sep 2, 2016

Hi!

My 95th percentile graph is not counting it right. It's about half of the real value.
Example graphs:
https://tobiasa.se/pub/95th.png
https://tobiasa.se/pub/95th2.png

Here you see the trend before the bad calculation showed up:
https://tobiasa.se/pub/history.png

Compare to Cacti which shows the right 95th value:
https://tobiasa.se/pub/cacti.png

Let me know if any more information is needed.

Version info:
Commit SHA: f278a92
DB Schema: 131
PHP: 5.6.24-0+deb8u1
MySQL: 5.5.50-0+deb8u1
RRDTool: 1.4.8
SNMP: NET-SNMP version: 5.7.2.1

/Tobias

@laf
Copy link
Member

laf commented Sep 6, 2016

What links are those graphs from?

@laf
Copy link
Member

laf commented Sep 7, 2016

I can't duplicate this, both my home and work installs seem to show the correct values.

image

@twindh
Copy link
Author

twindh commented Sep 16, 2016

This is still causing a lot of billing troubles for us. Is there any update on this?
Let me know if you need any debug data and I'll provide it.

@twindh
Copy link
Author

twindh commented Sep 17, 2016

Another issue we have seen is zero bytes 95th:
graph

Not sure if this is related to #3524 ?

@f0o
Copy link
Member

f0o commented Sep 21, 2016

Issue was due to wrong snmp ifspeed reporting. The billing-poll limits the data to the ifspeed. His ports were reporting 1G and the bills all flatline at 1G. Once changed to 10G the bills got the correct data accounted.

@f0o f0o closed this as completed Sep 21, 2016
@lock lock bot locked as resolved and limited conversation to collaborators May 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants