Provide support for using AND logic for triggers

[tomkerkhove]

Proposal

Allows end-users to scale out/in when the queue depth is high enough, and it is within a given time window, for example

Use-Case

Provide support for using AND logic for triggers so that it scales when all triggers meet the criteria

Anything else?

No response

[JorTurFer]

I think we can close this because it's not doable without formulas (and they already have its own issue) because it's the HPA Controller who does it, KEDA only exposes the raw metrics.
WDYT?

[tomkerkhove]

I don't really agree as the formula should be transparent to the end-user.

If I have two triggers, I should simply be able to say scale when both meet the criteria and not worry about writing formulas.

(That does not mean formulas are bad, but they serve a different audience)

[JorTurFer]

Right now we have these 2 issues related with this:
Composed (Logical/Priority) Triggers
Support custom formula for multiple metrics

could anyone of them match with this? just to not duplicate issues

[tomkerkhove]

#3330 is related but not 100% the same, #2440 is what this feature should build on but not solve my needs.

And then there is also #2614 but that's more advanced and for later on imo

[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.

[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.

[stale]

This issue has been automatically closed due to inactivity.

[joebowbeer]

@tomkerkhove Close this?

It can be implemented using a formula applied to a cron trigger and a queue trigger, right?

[zroubalik]

I belive we could close this, wdyt @tomkerkhove ?

[tomkerkhove]

I'd personally say we need to have explicit docs on doing AND operations. It feels like these formulas are the new silver bullet; but I personally argue that this is too technical and the UX for this should be simpler.

If somebody wants to do AND; we need to provide a knob and we'll build the formula for them.

[tomkerkhove]

This is why I believe we need a simpler and more integrated way to do AND: #6086