-
-
Notifications
You must be signed in to change notification settings - Fork 199
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
fix: prometheus with multiple providers #915
fix: prometheus with multiple providers #915
Conversation
Pull Request Test Coverage Report for Build 11c27a7f6-PR-915
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This is so much simpler, and the better solution! Thank you!
4cc179c
to
cc395c9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow! That's way cleaner. Thanks for sticking with it!
cc395c9
to
53cffad
Compare
Aight, that should be it. @gdey Some minor things on the hana provider like casing of errors and unhandled errors. Can you take one last look please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you are forgetting to pass in the provider name to the connection pool for the Hana driver. @mrylov Can you give this a quick review as well? Thank you.
we encountered an issue where tegola would panic if you'd try to register duplicate metrics collectors. that would happen if you have more than one mvt provider in the same config file. this fix makes provider metrics unique by adding the respective provider name to an array of constant labels. Upon collecting metrics on start up we'd pass unique metrics to the registration step. resolves: go-spatial#886 chore: fixing casing chore: add constant labels to hana provider fix: add provider name to connection pool
53cffad
to
2d42670
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
we encountered an issue where tegola would panic if you'd try to register duplicate metrics collectors.
that would happen if you have more than one mvt provider in the same config file.
this fix makes provider metrics unique by adding the respective provider name to an array of constant labels. Upon collecting metrics on start up we'd pass unique metrics to the registration step and avoid said panic.
resolves: #886