You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to have the option to suppress the error of reading nil value as reading 0 in using application insights.
Use-Case
My use case is as follows:
I have a metric which only logs when there are incoming requests to the service. During the period of no requests, there will be no metrics. This caused the issue that over a time span with no activity, I am reading nil value over that metric, and this will put the scaled object into fallback (which I do not want) and flood the keda operator logs with error logs.
It would be great if there is an option to ignore the nil value error.
Is this a feature you are interested in implementing yourself?
No
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Thank you for your replay. I saw that option in prometheus Scaler, and yes this is exactly what I want.
However, the issue is that I am using azure application insight scaler, which does not support this feature at the moment.
Therefore, I would want to know if there is any work around possible in azure application insight scaler.
Thank you for your replay. I saw that option in prometheus Scaler, and yes this is exactly what I want. However, the issue is that I am using azure application insight scaler, which does not support this feature at the moment. Therefore, I would want to know if there is any work around possible in azure application insight scaler.
Thank you!
IMHO it is not, but we are open to contributions. It's quite easy task, you can take inspiration from the Prom scaler.
Proposal
Hi team,
I would like to have the option to suppress the error of reading nil value as reading 0 in using application insights.
Use-Case
My use case is as follows:
I have a metric which only logs when there are incoming requests to the service. During the period of no requests, there will be no metrics. This caused the issue that over a time span with no activity, I am reading nil value over that metric, and this will put the scaled object into fallback (which I do not want) and flood the keda operator logs with error logs.
It would be great if there is an option to ignore the nil value error.
Is this a feature you are interested in implementing yourself?
No
Anything else?
No response
The text was updated successfully, but these errors were encountered: