ying

@aryan9600 @stefanprodan can you help to review again and provide your feedback to see whether this idea to add a finalizing webhook is acceptable? Thanks!

I think this is a scaler specific issue. The Azure-data-explorer scaler used "s{n} + databasename" as metricName when creating the metric object, which does make troubles for monitoring purpose. i.e....

@JorTurFer , scaledobject name is not enough. Per KEDA docs, it is recommended to define multiple triggers for the same scaling target, ``` KEDA allows you to use multiple triggers...

@zroubalik , then how to resolve the monitoring pain point? See my example: When creating the trigger, I set 2 different trigger.metadata.metricName , one is "inProgressTaskNumber", another is "pendingTaskNumber", but...

@tomkerkhove , yes, `suffix` can work, but it should be unique for each trigger, not for "SO" (considering multiple triggers for one SO).

@zroubalik , if my understanding is correct, I can start to define trigger.name directly in current KEDA version. But to show the "name" in grafana, additional code changes to enable...

@JorTurFer , I didn't notice your comments .... Instead, I created a PR to fix the issue https://github.com/kedacore/keda/pull/3650 per the suggestion in above https://github.com/kedacore/keda/issues/3588#issuecomment-1227355883 by @zroubalik can you help to...

@dprotaso , I am running on k8s v0.17 with limit range : ``` spec: limits: - default: cpu: 100m defaultRequest: cpu: 100m max: cpu: "8" min: cpu: 10m type: Container...

@dprotaso , I think the similar issue also happens when the namespace has a resource quota or the cluster resource is exhausted. Sometimes, the resource quota breached or insufficient resource...

@dprotaso , can you help to share a little bit of the idea to fix this?