Bug 2304076
Summary: | duplicate metrics being produced | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | iwatson | |
Component: | Multi-Cloud Object Gateway | Assignee: | Aayush Chouhan <achouhan> | |
Status: | ASSIGNED --- | QA Contact: | Sagi Hirshfeld <shirshfe> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 4.16 | CC: | aakobi, abhishku, achouhan, amark, dosypenk, ebenahar, etamir, jdelaros, jeremy.coulombe, julien.prost, kelwhite, lmauda, mmanjuna, muagarwa, nachahua, nbecker, nimrody, nthomas, odf-bz-bot, sbiradar, spasquie, ssonigra, yhuang | |
Target Milestone: | --- | |||
Target Release: | ODF 4.18.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | 4.17.0-117 | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
Prometheus client dependency upgrade caused process level metris (res mem, VSS, heap, etc.) to be collected when custom metrics are collected as well.
Consequence:
Duplicate metrics since NooBaa was collecting process level metrics as well as custom metrics. These dups caused an alert in Prometheus
Fix:
Remove process-level collections as those are collected now upon custom metrics.
Result:
Remove duplication of metrics reporting and the alert in Prometheus
|
Story Points: | --- | |
Clone Of: | ||||
: | 2321231 2322896 (view as bug list) | Environment: | ||
Last Closed: | 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 2321231, 2322896 |
Description
iwatson
2024-08-12 08:37:08 UTC
created KCS Greetings, due to this bug, any change in configmap cluster-monitoring-config could not be processed, so this is impacting new deployments to configure persistence. Hello team, Thank you for the information. I see the target for fix is approved for 4.17 bug fix cycle ..Is it possible to get a fix/patch in 4.16 while waiting for the 4.17 cycle? Please and thank you Adebi Hi, Fixing on an older version, while on a newer version, there is an issue, is a regression. We will fix it on 4.17, and consider it to be in one of the 4.16.z Best Regards, Liran. Please update the RDT flag/text appropriately. |