-
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
Problem with fetching Azure custom metric through Azure Monitor scaler #1965
Comments
Let's take a look but for what it's worth, Azure Monitor custom metrics do not always have parity with Application Insights which can require different API usage. |
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. |
Any update on the status of this? |
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. |
I believe this is still a problem. It does appear that Application Insights uses a different API than Azure monitor. Here's the doc: https://dev.applicationinsights.io/reference I created a PR to add an Application Insights scaler: However, this scaler may not be necessary as the Azure Log Analytics scaler can be used to read Application Insights metrics using the AppMetrics table. |
Yes that is correct, I have misread the original report - Sorry :)
This is true, for the workspace-based Application Insights instances. The classic ones are still supported for 2-3 years so think a dedicated scaler might be better indeed. |
Discussed in #1946
Originally posted by dymitrs July 10, 2021
Hi all,
It seems that the Monitor scaler does not work with some custom metrics from Application Insights.
According to docs and the PR, Custom Metrics are supported after those changes #1883.
The autoscaler works fine for "default" metrics but for my custom one I'm getting this error and it fails - log from Keda operator pod:
Expected behavior:
Metrics are read from Azure.
Actual behavior:
Error getting metric.
Steps to reproduce:
KEDA Version:
2.3.0
The text was updated successfully, but these errors were encountered: