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

[Discussion] What metrics should be available from an Orbi RBR850? #18

Open
instantdreams opened this issue Jan 7, 2025 · 3 comments
Open

Comments

@instantdreams
Copy link

Running netgear_exporter successfully and importing into prometheus, I see the following metrics:

netgear_client_scrape_errors_total
netgear_client_scrapes_total
netgear_last_client_scrape_duration_seconds
netgear_last_client_scrape_error
netgear_last_client_scrape_timestamp
netgear_last_info_scrape_duration_seconds
netgear_last_system_info_scrape_error
netgear_last_system_info_scrape_timestamp
netgear_last_traffic_scrape_duration_seconds
netgear_last_traffic_scrape_error
netgear_last_traffic_scrape_timestamp
netgear_system_info_scrape_errors_total
netgear_system_info_scrapes_total
netgear_traffic_scrape_errors_total
netgear_traffic_scrapes_total

I would expect more from the Metrics section of the readme file - is this a limitation of the Orbi?

@DRuggeri
Copy link
Owner

It's possible. The bulk of this code is the result of reverse engineering observed protocols and responses which may have changed since being written. This is because Netgear doesn't release an official spec.

Unfortunately, I no longer have a netgear router I can prod at, but debug level logging may help us understand what is going on. Can you try running at that level? Feel free to share results - I'm happy to give a best effort analysis and maybe be able to fix any code issues in the underlying library the exporter uses. If you have Go installed, you could possibly also run the test suite of the client lib linked against your router to see if there are obvious failures happening there.

Just be careful if you share debug output. It is VERY verbose (needed a lot for reverse engineering, haha) and will expose your router credentials if you don't scrub them.

@instantdreams
Copy link
Author

I've set my environment variables as follows:

NETGEAR_EXPORTER_URL=[router-url]
NETGEAR_EXPORTER_USERNAME=[username]
NETGEAR_EXPORTER_PASSWORD=[password]
NETGEAR_EXPORTER_INSECURE=true
NETGEAR_EXPORTER_TIMEOUT=4
NETGEAR_EXPORTER_CLIENT_DEBUG=true
NETGEAR_EXPORTER_FILTER_COLLECTORS=Client,SystemInfo,Traffic
NETGEAR_EXPORTER_METRICS_NAMESPACE=netgear
NETGEAR_EXPORTER_WEB_LISTEN_ADDRESS=:9192
NETGEAR_EXPORTER_WEB_TELEMETRY_PATH=/metrics
NETGEAR_EXPORTER_LOG_LEVEL=debug

I'm getting no log entries at the DEBUG level. Perhaps I've configured the settings incorrectly?

@DRuggeri
Copy link
Owner

So sorry for the delay. The only thing that comes to mind is to ask if you have the latest bin since the log level config option is new. But to confirm, you get absolutely no output, or you don't see client debug log output? I ask because they're separate parts of the codebase. If you can share the exact CLI command and output (of course with sensitive data redacted) I may be able to see something that gives us a better idea of what is going on.

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

2 participants