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
On the Grafana dashboards in OpenShift, I wonder why the ordinates are not labeled. Example: "API Request Duration by Verb - 99th Percentile" metric had a peak of "4" on a cluster. Now I'm used to read response times in milliseconds. Only when opening the details via "Inspect" in a separate tab I see that the metric rather uses seconds instead of milliseconds. "4ms" is less worrying than "4s" for a response time. Is there a specific reason that axes are never labeled? Either axis labels or unit names would help to read the charts more quickly without zooming into each metric separately.
On the Grafana dashboards in OpenShift, I wonder why the ordinates are not labeled. Example: "API Request Duration by Verb - 99th Percentile" metric had a peak of "4" on a cluster. Now I'm used to read response times in milliseconds. Only when opening the details via "Inspect" in a separate tab I see that the metric rather uses seconds instead of milliseconds. "4ms" is less worrying than "4s" for a response time. Is there a specific reason that axes are never labeled? Either axis labels or unit names would help to read the charts more quickly without zooming into each metric separately.
cluster-kube-apiserver-operator/manifests/0000_90_kube-apiserver-operator_05_api_performance_dashboard.yaml
Line 139 in 37df1b1
The text was updated successfully, but these errors were encountered: