-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Document which (observability) metrics are initialized and which not #5609
Comments
Hey @JorTurFer, if you can point me to an area within the code I should be looking at/around, I can help document this. |
Sorry for the slow response, we were in KubeCon xD IDK if we could check a way to init them, but I have no idea |
Thanks @JorTurFer and no worries on the slow response. I saw you and @zroubalik were busy at KubeCon. Great entertaining session BTW!! If you can assign this one to me, I'll dig in. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. |
@JorTurFer Apologies... I sat on this for far too long. I did some quick testing on this and saw that only the |
Yeah, if |
Sounds good. The PR should be ready for review. kedacore/keda-docs#1425 |
Proposal
We expose multiple metrics but not all of them are initialized. They aren't init because it's impossible, e.g: we can't init a metric about ScaledObject latencies if there isn't any ScaledObject. Other case is when users expect information about CPU/Memory (scalers not managed by KEDA metrics server, so we cannot expose some values)
This is something that we know, but we should explain this in docs to make users aware about these limitations
The text was updated successfully, but these errors were encountered: