Bug 2021766 - Observability - There's no data in cpu usage panel on Grafana Resource Optimization dashboard from OCP 4.9 cluster
Summary: Observability - There's no data in cpu usage panel on Grafana Resource Optimi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Core Services / Observability
Version: rhacm-2.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: rhacm-2.3.4
Assignee: Chunlin Yang
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-10 06:53 UTC by cqu
Modified: 2021-12-07 00:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-23 15:48:37 UTC
Target Upstream Version:
Embargoed:
bot-tracker-sync: rhacm-2.4.z+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github open-cluster-management backlog issues 17847 0 None None None 2021-11-10 14:13:08 UTC

Description cqu 2021-11-10 06:53:00 UTC
Description of the problem:
I found this issue on two env, OCP 4.9 cpu usage would not be displayed on the Grafana UI

Release version:

Operator snapshot version: 
2.3.4 RC1

OCP version:
OCP 4.9

Browser Info:

Steps to reproduce:
1. Deploy MCO CR
2. ObservabilityAddon are created and metrics data are displayed on the Grafana UI
3. Navigate to the ACM - Resource Optimization dashboard
4. There's no data in CPU usage panel
5. This issue only on OCP 4.9(local-cluster or managed cluster), but other OCP versions seem working as expected.
6. I tried to run quey on local-cluster which is ocp 4.9, there's no result search back
sum(node_namespace_pod_container:container_cpu_usage_seconds_total:sum_rate{cluster="local-cluster"}) by (namespace)

Comment 2 cqu 2021-11-10 07:14:32 UTC
DB Size panel in Kubernetes/etcd Cluster has a similar issue.

Comment 3 cqu 2021-11-17 03:43:49 UTC
This issue is fixed by 2.3.4 RC2, close it.


Note You need to log in before you can comment on or make changes to this bug.