Bug 2073330

Summary: Observabilityy - memory usage data are not collected even collect rule is fired on SNO
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: cqu
Component: Core Services / ObservabilityAssignee: Chunlin Yang <chuyang>
Status: CLOSED ERRATA QA Contact: Xiang Yin <xiyin>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhacm-2.5CC: cqu, jwakely, smeduri
Target Milestone: ---Flags: bot-tracker-sync: rhacm-2.5+
Target Release: rhacm-2.5   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-09 02:10:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description cqu 2022-04-08 08:31:50 UTC 
Description of the problem: When collect rule is fired on SNO, pod/container data are collected, like CPU, and most memory data. But memory usage are not collect on the related 5 dashboards, like `General/Kubernetes / Compute Resources / Workload`

Release version: 2.5.0-DOWNSTREAM-2022-04-05-06-20-55

Operator snapshot version:

OCP version: 4.10.3

Browser Info:

Steps to reproduce:
1. Deploy MCOCR on SNO
2. press the CPU usage and trigger the collect rule
3. When collect rule is fired, memory usage are not collect on the related 5 dashboards, like `General/Kubernetes / Compute Resources / Workload`
4. env info - https://docs.google.com/spreadsheets/d/1yg75xNpeO1i_K39D43FZmMauQe2d2OuJ1UjunX7jz3A/edit?pli=1#gid=1088931685&range=A5

Actual results:

Expected results:

Additional info:
Comment 1 bot-tracker-sync 2022-04-08 19:04:17 UTC 
G2Bsync 1093153578 comment 
 marcolan018 Fri, 08 Apr 2022 18:11:18 UTC 
 G2Bsync
In metrics-collector logs in local-cluster namespace, I only found the record that the collect rule "SNOHighCPUUsage" fired like below
```
level=info caller=logger.go:45 ts=2022-04-08T08:57:37.485333272Z component=collectrule/evaluator msg="collect rule fired" name=SNOHighCPUUsage labels="{rule_name=\"SNOHighCPUUsage\"}"
```
but I didn't find any log mentioned that rule "SNOHighMemoryUsage" fired. 
That means only CPU metrics of pods/containers collected is desired behavior. The memory metrics will not be collected until the memory collect rule fired.
Comment 3 cqu 2022-04-10 03:38:57 UTC 
Thanks Marco for your clarification. But base on your comments, why memory quota data are collected even CPU collect rule is fired, please see above attachment. Thanks.
Comment 7 errata-xmlrpc 2022-06-09 02:10:35 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Red Hat Advanced Cluster Management 2.5 security updates, images, and bug fixes), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:4956
Comment 8 melindaetinw81 2023-01-05 06:53:15 UTC Comment hidden (spam)
Comment 9 Thelma Carlisle 2023-01-19 09:47:30 UTC Comment hidden (spam)
Comment 10 smith5742 2023-02-03 08:54:13 UTC Comment hidden (spam)
Comment 11 thomas hrnty 2023-05-29 06:45:18 UTC Comment hidden (spam)
Comment 12 Ceryssavage 2023-06-21 08:01:25 UTC Comment hidden (spam)
Comment 13 Alfie Summers 2023-09-05 10:36:43 UTC Comment hidden (spam)
Comment 14 Ryan247Zook 2025-05-12 11:09:44 UTC Comment hidden (spam)