Jorge Turrado Ferrero

/run-e2e azure **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/7806748656)

/run-e2e azure **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/7892765094)

/run-e2e azure **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/8492056028)

/run-e2e azure **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/8492056397)

It's ready to merge from code pov (just pending to rebase main branch). But I think that waiting until v2.14 is released could be a good idea because I'm not...

Hello @Adityashar Thanks for reporting the issue. We are currently working on another solution via integrating the DD Agent as a source for querying the metrics: https://github.com/kedacore/keda/issues/5355 This will improve...

> Does this mean that we would need Datadog's APIService to use this feature? Also IIRC, there can only be one APIService in a cluster for the `external.metrics.k8s.io`, i.e., either...

This is an interesting point. We aim to prevent all the panics by code instead of just recovering them, but maybe we could recover panics on scaler metric requests: https://github.com/kedacore/keda/blob/1e1cfb11d6ca826d7c083e9aba730e08f3bd24f4/pkg/scaling/cache/scalers_cache.go#L125-L142...

Are you willing to open a PR with this recover @cyrilico ?

Hello, The Grafana dashboard is en example to generate your own based on it, but it uses some metrics that can be in your cluster or can not be. Why?...