Metrics Errors #55
Labels
bug
Something isn't working
Comments
|
I'll move the conversation over here @jcouzy, I updated my OC200 to 5.6.4 to see if I could replicate it, and I can't seem to replicate the issue you're having... Could you send a full container log over, if possible? |
|
These are the errors I keep receiving; so basically all the metrics are there, but seem not to be collected. An error has occurred while serving metrics: 144 error(s) occurred:
|
|
Hi I do also have this issue. Same errors on stdout. |
|
Short update, I checked all version from v0.7.1 to 0.6.0. |
|
I can confirm that version 0.6.0 works for me as well, error free. |
|
v0.7.0 is when some changes were made to use collectors, so it makes sense the error disappears when reverting. Strange I'm not seeing this locally, I'll try and do a bit of digging to see why it's registering the collectors multiple times |
|
Are you only seeing this on Could you give me a bit more details about your setup to help me diagnose this better as I can't recreate the error at all on my end.
I'm suspecting the Omada API is returning duplicates somewhere but I can't quite pinpoint where |
|
I added the output of the As you can see this is only on the My prometheus configuration: Scraping is done in an 15s intervall. But the curl actually gives the error too. I have in total 5 devices. I am only using the default site, so one site in total |
|
My prometheus config:
So the default prometheus config parameters My devices: |
Merged
|
Okay, I've just made some changes to logging so you'll be able to dump the raw API responses, that will allow me to mock your setup locally and see if I can recreate this issue. If you could run version 0.8.0 of the exporter with the Just be aware - this will be the raw output straight from Omada, so you might want to double check there's no sensitive data in the log! (My output seemed fine, but you might want to check anyway) |
|
Hi, I did it. Used the 0.8.0 tag and enabled debug log. |
|
For some reason, the Omada API was returning duplicate ports, so for your 8 port switch, it was returning 16 ports but all of them were duplicated... Thanks for the logs, they were a massive help pinpointing the issue! I've added a simple but hacky fix as part of Let me know if you're still having trouble and I can re-open this issue |
|
Thanks for fixing this problem. I see metrics and no errors. Thanks for this tools. |
|
The fix works for me as well, thanks for fixing the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Discussed in #54
Originally posted by jcouzy November 22, 2022
Hi, when I run the Omaha_exporter in docker container is get errors when trying to access the metrics on http://hostname:9202.
I run the container like this:
docker run -d --name=omada-exporter -p 9202:9202 -e OMADA_HOST='https://omada.infra.local' -e OMADA_USER='prometheus' -e OMADA_PASS='*************' -e OMADA_INSECURE=true chhaley/omada_exporter
When I try to access the metrics, I receive these errors:
An error has occurred while serving metrics:
144 error(s) occurred:
And on and on.
What am I doing wrong?
The text was updated successfully, but these errors were encountered: