You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an issue that the metric istio.io/service/server/response_latencies that HPA collected is different to the value I see on cloud monitoring. I have enabled Anthos service mesh on the cluster, and installed custom-metrics-stackdriver-adapter on the gke cluster. Already set enable-distribution-support=true for deployment custom-metrics-stackdriver-adapter to enable getting distribution metrics like istio.io/service/server/response_latencies. but the metric of istio.io/service/server/response_latencies that HPA collected is too high compares to that metric show on the cloud monitoring (for example: 6144s compares to 3.12s). Here is the information:
Dear team,
I have an issue that the metric
istio.io/service/server/response_latencies
that HPA collected is different to the value I see on cloud monitoring. I have enabled Anthos service mesh on the cluster, and installed custom-metrics-stackdriver-adapter on the gke cluster. Already setenable-distribution-support=true
for deployment custom-metrics-stackdriver-adapter to enable getting distribution metrics like istio.io/service/server/response_latencies. but the metric ofistio.io/service/server/response_latencies
that HPA collected is too high compares to that metric show on the cloud monitoring (for example: 6144s compares to 3.12s). Here is the information:v1.24.10-gke.2300
gcr.io/gke-release/custom-metrics-stackdriver-adapter:v0.13.1-gke.0
adapter_new_resource_model.yaml
HPA declaration:
The metrics that HPA collected as follow:
The metric that show on monitoring:
Is there anything wrong here or I mis-understand something?
The text was updated successfully, but these errors were encountered: