Jorge Turrado Ferrero

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

There isn't anyone working on this, and we can request a dynatrace account for e2e tests, so there isn't any blocker if you are willing to work on this 😄

so, the stage is yours xD

We have the account ready, I just need to know which secrets you need and on which envs vars. For example, you can see how Datadog e2e test work: https://github.com/kedacore/keda/blob/main/tests/scalers/datadog/datadog_test.go#L252-L254...

I've created them: - DYNATRACE_HOST: https://IDENTIFIER.apps.dynatrace.com/ - DYNATRACE_METRICS_TOKEN: a token with metric scopes (ingest, read, write) Let me know if you need something else from my side 😄

> Thanks @JorTurFer ; I believe to use the API the host must be in the format `https://.live.dynatrace.com` (at least that's what I need to use with another installation I...

That url redirects to the `https://identifier.apps.dynatrace.com/` one, maybe both are supported 🤷 Let's add the e2e tests and when we trigger it in the testing infra we will discover it...

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

The e2e failure isn't related with this changes

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