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:
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.
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.
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
This comment was flagged a spam, view the edit history to see the original text if required.
A commitment of appreciation is all together for the association, keep on sharing such an information. https://www.baycarepatientportal.net/
ok for the info i will try to figure it out for more https://www.gomedicare.onl/
Check the collection rule configuration: Verify that the collection rule is correctly configured to collect memory usage data. Ensure that the conditions, schedule, and data collection settings are set appropriately. Review the event logs: Check the event logs or logs specific to the data collection process in ServiceNow to identify any errors or issues related to the memory usage data collection. https://www.myccpay.me/
Thanks for the information... https://www.mybkexperience.one/
Thanks for sharing. it's so interesting. https://www.yourtexasbenefits.bid/