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

Bits in Overall peering graphs #75

Closed
bcix opened this issue Sep 22, 2013 · 1 comment
Closed

Bits in Overall peering graphs #75

bcix opened this issue Sep 22, 2013 · 1 comment

Comments

@bcix
Copy link
Contributor

bcix commented Sep 22, 2013

Hey,

when I compare the In- and Out-bits in the "Overall peering graphs",
numbers are different to the values which a generated by MRTG itself in the "ixp_peering-bcix-total-bits.html" file.

See the two screenshots attached. Feature or Bug ?

mrtg_total_mrtg_html
mrtg_total_ixp_manager

Cheers, Thorleif

@nickhilliard
Copy link
Member

"Feature or Bug?" Yes.

IXP Manager parses mrtg log files and picks out slightly different values for the graphs than standard mrtg.

For the daily 5 minute graph, ixp manager selects the actual reading over the previous 300 second sample interval (i.e. second line of log file), whereas mrtg picks up the third line. There are similar differences for the weekly / monthly / annual graphs.

It's been a couple of years since I've looked at this code and I remember being frustrated at the time about the lack of documentation for how mrtg calculated these values. The code is in Mrtg.php if you want to take a look at it. I think it's correct, although I do understand that it is usually slightly (but not very much) different to the values that stock mrtg provides.

barryo pushed a commit that referenced this issue Oct 27, 2017
* house keeping

* [BF] - Viewing IP addresses throws an unexpected error - fixes islandbridgenetworks/IXP-Manager-Archive-Yann#74
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant