Provide support for autoscaling based on HTTP response time

[KowsikRS]

Keda autoscaling based on HTTP response time. If there is a delay in response time , KEDA should auto-scale the pods

[nrukavkov]

I think it could be worst for k8s cluster because we do not know the reason why response time is growing. It could be critical cpu usage and then autoscaling based on HTTP response time could make it worse

[KowsikRS]

If CPU usage is critical you can add CPU trigger for autoscaling

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

[vitobotta]

I would like scaling based on response time too or something like that. Besides that, how can I combine an HTTPScaledObject with CPU metrics for scaling? Thanks

[tomkerkhove]

@arschles Does our current spec allow scaling with other built-in KEDA scalers? I don't think so? If it does not, I'll open an issue

[JCMais]

did anyone figure out how to use this + the CPU scaler?

[JorTurFer]

did anyone figure out how to use this + the CPU scaler?

Currently, it's not supported because the HTTPScaledObject doesn't support any other source than the HTTP metrics.
This PR was promising, but it looks stale

[devopsdynamo]

I've created new PR which will allow for HTTP scaler to be used alongside other scalers.
#929

[JorTurFer]

This seems that has been stale for a long time. I close this as thanks to #929 there is a workaround now. If someone thinks that this is still something required, let's open another issue and discuss the best design considering current features