-
Notifications
You must be signed in to change notification settings - Fork 77
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
Support for application-specific metrics tracking #1220
Labels
enhancement
New feature or request
Comments
The changes would be to following:
To test this functionality we will need to create an application that collects some metrics and exposes them on such an endpoint. |
devdattakulkarni
changed the title
Support for application-specific metrics tracking.
Support for application-specific metrics tracking
Apr 16, 2024
devdattakulkarni
changed the title
Support for application-specific metrics tracking
Add support for application-specific metrics tracking
Apr 16, 2024
devdattakulkarni
changed the title
Add support for application-specific metrics tracking
Support for application-specific metrics tracking
May 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, KubePlus tracks the following metrics by default: CPU, memory, ingress network, egress network, and storage. We should support the ability to track application-specific metrics through ResourceMonitor CRD. The assumption here will be that the application exposes such metrics at some endpoint that KubePlus is able to scrape and surface out for ingesting into Prometheus.
The text was updated successfully, but these errors were encountered: