-
Notifications
You must be signed in to change notification settings - Fork 403
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
router: fix prometheus metrics high cardinality issue #789
Conversation
Closes #448 Refers to [CVE(internal)](https://github.com/helm/chartmuseum/security/advisories/GHSA-67g5-8r7h-h9qv) Signed-off-by: scbizu <[email protected]>
ce3a8f2
to
f81ffa4
Compare
Signed-off-by: scbizu <[email protected]>
f81ffa4
to
9e3de5b
Compare
Signed-off-by: scbizu <[email protected]>
Signed-off-by: scbizu <[email protected]>
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
Sorry to add noise, but any reason this hasn't been merged? The metrics cardinality issue is affecting my production, so I'd be happy to help get this merged. |
@AnotherKamila Sorry , I've almost forgot this PR , really busy these days 😣 . I will back to this again . |
* deprecate the external dependency of go-gin-prometheus * use zap logger(cm) replace of logrus logger(go-gin-prometheus) for better investigation Signed-off-by: scbizu <[email protected]>
Hi @cbuto , as we talked before (if I remember it's right) , I've moved the prometheus middleware inside CM , and remove the outside dependency as it is not maintained recently. Please take a look again ? (And I add the toolchain in go.mod 😆) |
@AnotherKamila Try to bump to the canary image to get the bug fixed 👋 |
Closes Possibly high cardinality on chartmuseum_requests_total labels #448
Refers to CVE(internal)