Bug 2256458

Summary: [release-4.14] Provide better logging for ocs-metrics-exporter
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: umanga <uchapaga>
Component: ceph-monitoringAssignee: umanga <uchapaga>
Status: CLOSED ERRATA QA Contact: Filip Balák <fbalak>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.14CC: hnallurv, kramdoss, odf-bz-bot
Target Milestone: ---   
Target Release: ODF 4.14.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.14.4-2 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 2256456 Environment:
Last Closed: 2024-01-22 10:53:02 UTC Type: ---
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: 2256456, 2256459    
Bug Blocks:    

Description umanga 2024-01-02 12:45:26 UTC 
+++ This bug was initially created as a clone of Bug #2256456 +++

Description of problem (please be detailed as possible and provide log
snippests):

ocs-metrics-exporter logs are not good enough to identify some of the internal errors and the log format is not structured.

Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
No

Is there any workaround available to the best of your knowledge?
No

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:
Not a regression.

Steps to Reproduce:
1.
2.
3.


Actual results: Logs do not have enough information about internal errors.


Expected results: Logs should have enough information about internal errors.


Additional info:

--- Additional comment from RHEL Program Management on 2024-01-02 18:12:18 IST ---

This bug having no release flag set previously, is now set with release flag 'odf‑4.15.0' to '?', and so is being proposed to be fixed at the ODF 4.15.0 release. Note that the 3 Acks (pm_ack, devel_ack, qa_ack), if any previously set while release flag was missing, have now been reset since the Acks are to be set against a release flag.

--- Additional comment from umanga on 2024-01-02 18:14:12 IST ---

Fixing this will help with debugging some issues which are extremely difficult to catch.
Providing devel_ack+ .
Comment 7 Filip Balák 2024-01-15 13:16:28 UTC 
Logs are in json format with a clear timestamp (as requested by reproducer from https://bugzilla.redhat.com/show_bug.cgi?id=2256456#c7). Example:

{"level":"info","ts":1705187947.6389065,"caller":"cache/rbd-mirror.go:321","msg":"RBD mirror store resync ended at 2024-01-13 23:19:07.638899431 +0000 UTC m=+475164.855126630\n"}
{"level":"info","ts":1705187952.6032627,"caller":"cache/ceph-blocklist.go:106","msg":"Blocklist store sync started 2024-01-13 23:19:12.603222165 +0000 UTC m=+475169.819449365\n"}
{"level":"info","ts":1705187953.0969985,"caller":"cache/ceph-blocklist.go:134","msg":"Blocklist store sync completed at 2024-01-13 23:19:13.096955914 +0000 UTC m=+475170.313183192\n"}
{"level":"error","ts":1705187956.243121,"caller":"collectors/ceph-block-pool.go:137","msg":"Invalid image health for pool cephblockpool-storageconsumer-d478e940-d154-4376-9a00-e5843abecad9-821baa86. Must be OK, UNKNOWN, WARNING or ERROR\n","stacktrace":"github.com/red-hat-storage/ocs-operator/v4/metrics/internal/collectors.(*CephBlockPoolCollector).collectMirroringImageHealth\n\t/remote-source/app/metrics/internal/collectors/ceph-block-pool.go:137\ngithub.com/red-hat-storage/ocs-operator/v4/metrics/internal/collectors.(*CephBlockPoolCollector).Collect\n\t/remote-source/app/metrics/internal/collectors/ceph-block-pool.go:82\ngithub.com/prometheus/client_golang/prometheus.(*Registry).Gather.func1\n\t/remote-source/app/vendor/github.com/prometheus/client_golang/prometheus/registry.go:455"}
{"level":"info","ts":1705187956.3687186,"caller":"collectors/object-bucket.go:256","msg":"No ObjectBuckets present in the object store ocs-storagecluster-cephobjectstore\n"}
{"level":"info","ts":1705187960.2152925,"caller":"cache/pv.go:244","msg":"PV store Resync started at 2024-01-13 23:19:20.215232251 +0000 UTC m=+475177.431459580\n"}
{"level":"info","ts":1705187960.242822,"caller":"cache/pv.go:255","msg":"now processing: local-pv-306ad665\n"}
{"level":"info","ts":1705187960.2430336,"caller":"cache/reflector.go:458","msg":"/remote-source/app/metrics/internal/collectors/registry.go:63: watch of *v1.PersistentVolume ended with: failed to process PV: local-pv-306ad665 err: unexpected object of type v1.PersistentVolume\n"}
{"level":"info","ts":1705187961.5355313,"caller":"cache/pv.go:102","msg":"PV store addition started at 2024-01-13 23:19:21.535496854 +0000 UTC m=+475178.751724062 for PV local-pv-306ad665\n"}
{"level":"info","ts":1705187961.5355744,"caller":"cache/pv.go:106","msg":"Skipping non Ceph CSI RBD volume local-pv-306ad665\n"}
{"level":"info","ts":1705187961.5355844,"caller":"cache/pv.go:102","msg":"PV store addition started at 2024-01-13 23:19:21.535580635 +0000 UTC m=+475178.751807830 for PV local-pv-3a2157c0\n"}
{"level":"info","ts":1705187961.5355928,"caller":"cache/pv.go:106","msg":"Skipping non Ceph CSI RBD volume local-pv-3a2157c0\n"}
{"level":"info","ts":1705187961.5356004,"caller":"cache/pv.go:102","msg":"PV store addition started at 2024-01-13 23:19:21.535597613 +0000 UTC m=+475178.751824809 for PV local-pv-485e0557\n"}

No other metrics regression is found except for https://bugzilla.redhat.com/show_bug.cgi?id=2253429.

Tested with
OCS 4.14.4-4
Comment 11 errata-xmlrpc 2024-01-22 10:53:02 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 (Red Hat OpenShift Data Foundation 4.14.4 Bug Fix Update), 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/RHBA-2024:0315