-
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
Multiple Azure Log Analytics scalers doesn't work with the same workspace #2100
Comments
Hi Metric: v2beta2.MetricIdentifier{
Name: kedautil.NormalizeString(fmt.Sprintf("%s-%s", "azure-log-analytics", s.metadata.workspaceID)),
}, Honestly, I don't have any idea about how we could generate it automatically without collisions in this case. |
@JorTurFer agree, adding Side note: we should probably refactor the code and solve the |
I will work on this today and I will create the PR ASAP |
We will use a similar approach for all scalers #2123, instead of just this one. |
Report
When trying to have at least two
Azure Log Analytics
scalers working for the same workspace/namespace we have an error with uniqueexternalMetricName
validation, since name for that is actually made like this:azure-log-analytics- {{workspaceId}}
Expected Behavior
Having option to deploy more then one Azure Log Analytics scaler for specified workspace.
Actual Behavior
While defining more than one scaler for Azure Log Analytics, it throws error about uniqueness violation.
Steps to Reproduce the Problem
Logs from KEDA operator
KEDA Version
2.3.0
Kubernetes Version
1.20
Platform
Microsoft Azure
Scaler Details
Azure Log Analytics
Anything else?
No response
The text was updated successfully, but these errors were encountered: