Emit metric tracking empty responses from prometheus #7060
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We'd like to have a way to monitor the number of Keda errors due to empty responses from prometheus after enabling the
ignoreNullValues
flag for most of our prometheus triggers.Right now this error gets logged but the error metric that Keda emits is generic and doesn't differentiate by error type.
Checklist
When introducing a new scaler, I agree with the scaling governance policyN/AA PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)N/AFixes #7062