Jorge Turrado Ferrero

I missed this issue, sorry :( Could you try upgrading KEDA to a greater version?

Hello, What KEDA version are you using? this error shouldn't happen because KEDA tries to reconcille the ScaledObjects automatically. Do you see any error in KEDA ooperator logs?

I'm going to try to reproduce this. From your example, I understand that I can deploy the ScaledObject and then, after some seconds, the external gRPC server and it'd be...

Hello, Do you mean that you want to scale based on HTTP traffic? You can currently do it using an indirect measure (for example, scrapping the ingress metrics using prometheus...

Hello, Which is the problem exactly? The value using `m` (1040334m)? In K8s context 'm' means `mili` and it's used when the value is a float number because k8s doesn't...

Are you scrapping prometheus metric generated by KEDA? I almost sure that you have a peak which justifies the scaling out, as you said, you're under the threshold. The only...

No no, it doesn't use the average value at all. KEDA uses the current value, so if it's 0 in the eventhub and you don't see 0 in KEDA, it...

> /run-e2e nonsense **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/9125967954) This won't help here, because the workflow is executed from `main` branch because it's a comment flow

Awesome catch! Thanks for the fix :heart:

Hello @gerbil It's working as expected because the scaling to 5 is happening, as we can see here: ``` 2024-05-15T10:33:11Z INFO scaleexecutor Successfully set ScaleTarget replicas count to ScaledObject minReplicaCount...