-
Notifications
You must be signed in to change notification settings - Fork 6
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
Rate limits #6
Comments
Hi there, @jcwimer. I can't say I'm an expert in their SOAP API server since, at least at the time I wrote this exporter, they still have not published any consumer information. Based on my own experiences with the Orbi platform, I would be surprised if the SOAP server maintained a rate limiter... in my own experiences, it is very possible to overload the CPU on the router by scraping a lot of extra metrics. I saw this on my own network when enabling the client information for this exporter, for example. When enabled, I would see random network dropouts that coincided with scrapes. Do you happen to have client information being scraped, too? Have you tried tweaking the timeout at all? |
I tweaked the timeout to 15s as it would take 11.5s on average to complete a request if I went to it from a browser or a curl. I am working now to restrict the info to only traffic info as I do not need anything else and I remember seeing that the router was at 75% CPU when I scrolled through the text sent back. Thanks for that tip. I will close this issue if that solves this. |
How does the filter work with the |
I tried adding
|
Thanks, @bwees - you're correct - the |
I am using version 1.0.1 according to the output of the command. |
Hrm... that's.... odd. I don't recall ever releasing a |
I'll go ahead and close this in the hopes that everything's square. If that's not accurate, feel free to add a comment and let me know what your results are. |
Do you know if there are rate limits on the router's soap server? I have been pinging it every 15 sec to be able to do some bandwidth calculations and there are "holes" in the data where it times out, I have the timeout set to 5 seconds. Here is the errors that I get:
level=error msg="Error while collecting client statistics: Post \"http://10.0.1.1/soap/server_sa/\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" source="clients_collector.go:122"
and
the Netgear_client login error does not appear frequently, about 1 time for every 10 of the first error.
The text was updated successfully, but these errors were encountered: