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.

Sign up for GitHub

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

Jump to bottom

Provide a metric for total amount of ScaledObjects #2637

Closed
tomkerkhove opened this issue Feb 15, 2022 · 5 comments
Closed

Provide a metric for total amount of ScaledObjects #2637

tomkerkhove opened this issue Feb 15, 2022 · 5 comments
Assignees
@v-shenoy
Labels
feature All issues for new features that have been committed to Hacktoberfest help wanted Looking for support from community prometheus system-metrics

Comments

@tomkerkhove
Copy link
Member

Proposal

Provide a metric for total amount of ScaledObjects so that end-users can visualize it.

Use-Case

Improve our operational story

Anything else?

No response
@tomkerkhove tomkerkhove added needs-discussion feature-request All issues for new features that have not been committed to labels Feb 15, 2022
@tomkerkhove tomkerkhove moved this to Proposed in Roadmap - KEDA Core Feb 15, 2022
@tomkerkhove tomkerkhove added feature All issues for new features that have been committed to prometheus system-metrics help wanted Looking for support from community and removed needs-discussion feature-request All issues for new features that have not been committed to labels Feb 15, 2022
@liangyuanpeng
Copy link
Contributor

I want to work for it, can you give me some help? Thanks.

Have a question: where is the appropriate place to implement this, is it port of 9022 from keda-operator-metrics-apiserver?

@zroubalik
Copy link
Member

Yeah, probably yes, given the current implementation.

Though we should think about this as well: #1281

@tomkerkhove tomkerkhove mentioned this issue Jun 1, 2022
Closed
@bamboo12366
Copy link
Contributor

Can consider adding update hpa error and active polling rate/error rate as well IMHO
As I mention in this issue #3098, those are both key metrics in my use-case

@tomkerkhove
Copy link
Member Author

This is nto really related here but created #3120

@tomkerkhove tomkerkhove moved this from Proposed to To Do in Roadmap - KEDA Core Jun 2, 2022
@v-shenoy v-shenoy mentioned this issue Oct 2, 2022
Merged
4 tasks
@tomkerkhove tomkerkhove moved this from To Do to In Progress in Roadmap - KEDA Core Oct 3, 2022
@tomkerkhove tomkerkhove assigned v-shenoy and unassigned raorugan Oct 3, 2022
@tomkerkhove tomkerkhove mentioned this issue Oct 10, 2022
Merged
1 task
@v-shenoy
Copy link
Contributor

v-shenoy commented Nov 7, 2022

Closed in #3719

@v-shenoy v-shenoy closed this as completed Nov 7, 2022
Repository owner moved this from In Progress to Ready To Ship in Roadmap - KEDA Core Nov 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@v-shenoy v-shenoy

Labels
feature All issues for new features that have been committed to Hacktoberfest help wanted Looking for support from community prometheus system-metrics
Projects
Roadmap - KEDA Core
Archived in project
Milestone
No milestone
Development

No branches or pull requests
6 participants
@zroubalik @tomkerkhove @liangyuanpeng @bamboo12366 @v-shenoy @raorugan