Excessive calling of the DD API by KEDA about keda

[JorTurFer]

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 Keda or Datadog.

I don't think so, that path is the path exposed by the server, so the idea is that you will have to install the DD Agent without registering the APIService. Then you can set the DD service endpoint in KEDA and KEDA will query the DD Agent without registering the APIService

[JorTurFer]

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: #5355

This will improve the behavior and relies on the agent the rate limiting management.

I'm not totally sure about adding a retry/delay system because it'll be released probably at the same time as the support for DD Agent and it'll handle the situation quite better, but I'm not against of it.
@zroubalik @tomkerkhove ?

[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: #5355
This will improve the behavior and relies on the agent the rate limiting management.

Thanks for this information @JorTurFer, looking forward to this feature!

[zroubalik]

I agree with @JorTurFer

[Adityashar]

@JorTurFer @zroubalik I was taking a look at @arapulido's draft code and saw this line:

keda/pkg/scalers/datadog_scaler.go

Line 151 in 76a58a9

return fmt.Sprintf("https://%s.%s.svc.cluster.local:%d/apis/external.metrics.k8s.io/v1beta1", datadogMetricsService, datadogNamespace, datadogMetricsServicePort)

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 Keda or Datadog.