-
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
Prometheus' metrics in the operator are only exposed when the metrics server requests the metrics #4075
Comments
Is this related to the fact that apart from Metrics exposed by the Operator SDK, I only see I was expecting to see |
So you don't see these values once you create a ScaledObject? |
I was able to see them after following this https://keda.sh/docs/2.9/operate/metrics-server/. Since most of the SOs only use CPU and Memory scalers, I read in another issue this is intended. I can now see:
Missing (according to docs):
The latest official Grafana dashboard depends on some of these metrics, in particular, |
So the supported metrics are (for 2.9.1.)
|
We will most likely release 2.9.2 soon, this should also fix the exported metrics. |
2.9.2 including fix this has been just released! |
Will try it and provide feedback @zroubalik. Thanks! |
Not sure if this was supposed to be fixed since I'm rolling with the latest release v.2.9.3 and I am having the same problem. I was trying to get the grafana dashboard to work but as @nunoadrego pointed out, the dashboard depends on some of these metrics. I'm also unable to set some most of the variables for the dashboard apart from the data-source. Any tips? |
Report
I have seen that metric
keda_scaler_metrics_value
is updated when the value is queried by the ms (and the same forkeda_scaler_error_totals
andkeda_scaled_object_error_totals
), I think that it makes sense to update the metric afterGetMetricsAndActivity
(insideGetScaledObjectState
) because it has been readKEDA Version
2.9.1
The text was updated successfully, but these errors were encountered: