Jorge Turrado Ferrero

It seems that the query isn't correct. Checking the logs I see lines like this: ```bash 2024-04-28T22:27:24Z ERROR dynatrace_scaler error executing Dynatrace query {"type": "ScaledObject", "namespace": "dynatrace-test-ns", "name": "dynatrace-test-so", "error":...

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

``` bash 2024-04-29T19:24:29.2272752Z === RUN TestDynatraceScaler 2024-04-29T19:24:29.2276455Z dynatrace_test.go:***9: --- setting up --- 2024-04-29T19:24:29.2280365Z helper.go:***48: deleting namespace dynatrace-test-ns 2024-04-29T19:24:29.2299743Z helper.go:***0***: waiting for namespace dynatrace-test-ns deletion 2024-04-29T19:24:29.2304187Z helper.go:***5: Creating namespace - dynatrace-test-ns...

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

Same result: ``` 2024-04-29T20:05:14Z ERROR dynatrace_scaler error executing Dynatrace query {"type": "ScaledObject", "namespace": "dynatrace-test-ns", "name": "dynatrace-test-so", "error": "dynatrace response does not contain any metric series"} ``` Is this metric correct?...

I've been on a business trip this week, but let me check out your branch and check the current code using the current secrets

hum... It seems that the certificate isn't hot reloaded on changes. I think that we have to add a watcher for the cert files and restart the server in case...

The problem is that the log you sent says problems validating the cert, not just the connection but the cert, that's the weird part for me :/

Could you check the secret which contains the cert to verify if it was recreated ? (checking the certificate creation time, not just the secret). I see `notBefore: "2024-04-04T06:08:03Z"` so...

Hello, This is weird and it shouldn't happen. Are you willing to take a look and open a PR with the fix?