-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Datadog trigger is being included into the composite-metric unexpectedly. #5367
Comments
Hello, |
@JorTurFer Thank you for guiding. However, for now, I have to use cron trigger with scalingModifiers. Any workarounds or plans for this feature? |
I don't think so, because it makes the things quite complex (which metrics, why onyl one formula, etc), but I'd like to know the thoughts from @zroubalik and @tomkerkhove |
Yeah, I am also inclined towards what @JorTurFer mentioned. The original desing of ScalingModifiers have been done this way. It would be extremely complicated. Just include it into the formula. |
Report
I am using scalingModifiers to make composite-metric using metric-api triggers but when I add datadog trigger metric, it's also forced to be included into composite-metric not as I expected.
Expected Behavior
I expected the new external section to be added in HPA.
Actual Behavior
I am using scalingModifiers to make composite-metric using metric-api triggers but when I add datadog trigger metric, it's also forced to be included into composite-metric not as I expected.
Steps to Reproduce the Problem
Logs from KEDA operator
KEDA Version
2.12.1
Kubernetes Version
1.26
Platform
Amazon Web Services
Scaler Details
kubernetes-workload, metrics-api, cpu, datadog
Anything else?
We are operating k8s using kops on AWS.
The text was updated successfully, but these errors were encountered: