-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Improve Prometheus Metrics #3716
Labels
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
kind/feature
Categorizes issue or PR as related to a new feature.
Comments
Related #3244 |
Thank you for raising the issue! We will be taking a look at it, and of course we also welcome any community contributions to address the issue as well. |
Thanks @huangm777, ended up finding some metrics I could use, namely the aws_api ones. Still I think I would benefit from having some of these documented. When I find time I'll try to open a PR for this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
kind/feature
Categorizes issue or PR as related to a new feature.
Is your feature request related to a problem?
I couldn't find any documentation for what metrics the "metrics-server" port exposes.
Additionally, I couldn't configure the Helm Chart to not scrape these metrics, as my scrape_configs are looking at the prometheus.io/* annotations and these cannot be removed without enabling a ServiceMonitor.
Describe the solution you'd like
Describe alternatives you've considered
N/A
The text was updated successfully, but these errors were encountered: