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

Realtime 1s #2292

Closed
lbsou opened this issue Jan 8, 2019 · 5 comments
Closed

Realtime 1s #2292

lbsou opened this issue Jan 8, 2019 · 5 comments
Labels
bug Undesired behaviour enhancement General tag for an enhancement resolved A fixed issue

Comments

@lbsou
Copy link

lbsou commented Jan 8, 2019

Hi !

I would like to know if it would be possible to get module realtime to poll data at 1 sec interval.

Our 3750 and 3600 update IfOutOctets and IfInOctets every seconds.

As the next question will be why would you want to do that, I will answer straight away

We dont have console access to the switch, only snmp view and we manage approx. 2000 of them.

When we need to clarify to a customer that either he need to activate QoS or that there is no saturation, I want to be as precise as I can. I don't need that polling on every day basis, only when we do diagnostic.

Thank you!
Louis

@netniV
Copy link
Member

netniV commented Jan 8, 2019

tbh, and this is just my opinion - others may have a better idea, for something like that I think you would be better off writing a script that uses SNMPGET or SNMPWALK and writes the values to a file. Then parse that file with something like excel to generate a graph purely for speed.

If you are utilising Cacti, as fast as it can be, there will still be overheads for all the components including the serving of the graph images and website.

For truely accurate data, you'd either need a 1 second poller or a constantly running script.

@cigamit
Copy link
Member

cigamit commented Jan 8, 2019

You can also implement this yourself. Just edit include/global_arrays.php line 1400, follow your nose to add 1 second. Let us know if it's responsive enough and we can implement. Though 2 seconds might be better. Either way, let us know.

@cigamit cigamit added the enhancement General tag for an enhancement label Jan 8, 2019
@cigamit
Copy link
Member

cigamit commented Jan 8, 2019

You also have to edit poller_realtime.php and change the step on line 212 to initialize at something like 1, right now it defaults to what you have asked for. Likely a bit of a bad design (right now, the rrdfiles will be created at 10 second step, so if you change to 5, you don't get an update every polling.).

@cigamit
Copy link
Member

cigamit commented Jan 8, 2019

Works find for me. Took only a few minutes to do.

@cigamit cigamit added the bug Undesired behaviour label Jan 8, 2019
@cigamit
Copy link
Member

cigamit commented Jan 8, 2019

Marked as a bug due to interval setting step too granular. You will luck out in the 1.2.1 release.

@cigamit cigamit added the resolved A fixed issue label Jan 8, 2019
cigamit added a commit that referenced this issue Jan 8, 2019
Allow Realtime to use a one second collection frequency
@cigamit cigamit closed this as completed Jan 27, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Undesired behaviour enhancement General tag for an enhancement resolved A fixed issue
Projects
None yet
Development

No branches or pull requests

3 participants