-
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
Metrics Scaler: Improve Error Handling on not-ok response #2317
Comments
This seems like a fair request, are you willing to contribut this? |
I'd be happy to contribute, I'll look into the process and will link a PR |
Also while you're at it, this defer keda/pkg/scalers/metrics_api_scaler.go Line 219 in cbe929b
if r.StatusCode != http.StatusOK
|
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. |
@schoki040 what is the status of this please? |
I was not yet able to make any changes on this. This improvement is nonetheless still dear to my heart. Please dont close. |
Hey. I created PR for this issue. Please review - #2739 |
Proposal
What's even going on?
The Metrics API Scaler is pretty quit on non-200 API responses. (See this link for code)
At the moment we are using this for around 2000 scale targets and whenever something on API side goes wrong its a real hassle to even find out what the query was, when this is your response:
Suggestion
Integrate the requested API endpoint and an optional response body into the scale error to get decent info on why the query didn't go through.
Possible new log
Use-Case
Anything else?
No response
The text was updated successfully, but these errors were encountered: