Skip to content
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

Provide a metric for metric server performance #3120

Open
Tracked by #3698
tomkerkhove opened this issue Jun 2, 2022 · 2 comments
Open
Tracked by #3698

Provide a metric for metric server performance #3120

tomkerkhove opened this issue Jun 2, 2022 · 2 comments
Labels
feature All issues for new features that have been committed to help wanted Looking for support from community opentelemetry prometheus system-metrics

Comments

@tomkerkhove
Copy link
Member

Proposal

Provide a metric for metric server performance:

  • The rate and error rate to update HPA
  • The rate to query the so active

See #3098 (comment)

Use-Case

Monitor integration between HPA & metric server

Anything else?

Relates to #3098

@tomkerkhove tomkerkhove added help wanted Looking for support from community feature All issues for new features that have been committed to prometheus labels Jun 2, 2022
@tomkerkhove tomkerkhove moved this to Proposed in Roadmap - KEDA Core Jun 2, 2022
@tomkerkhove tomkerkhove moved this from Proposed to To Do in Roadmap - KEDA Core Jun 2, 2022
@pragmaticivan
Copy link
Contributor

What's going to be the client producer for the metrics? OpenTelemetry SDK or prom client?

@tomkerkhove
Copy link
Member Author

tomkerkhove commented Aug 1, 2022

We should have both but we can start with just Prometheus for now as we already have this in place.

Are you willing to contribute this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature All issues for new features that have been committed to help wanted Looking for support from community opentelemetry prometheus system-metrics
Projects
Status: To Do
Development

No branches or pull requests

2 participants