-
Bug
-
Resolution: Done
-
Minor
-
None
-
None
-
2
-
OpenShift SPLAT - Sprint 266
When running 'opct report' and the metrics is not corrected collected from archive for some reason, the report will raising the following message in the error log level:
$ opct-devel report --save-to results opct_202502041948_e68ef821-0d6a-4131-a135-e3dbb0dd7109.tar.gz --log-level=debug ... DEBU[2025-02-04T21:44:16-03:00] Chart/file saved results/metrics/index.js ERRO[2025-02-04T21:44:16-03:00] empty metric data, ignoring metric query_range-cluster-storage-iops.json.gz ERRO[2025-02-04T21:44:16-03:00] empty metric data, ignoring metric query_range-cluster-storage-throughput.json.gz DEBU[2025-02-04T21:44:16-03:00] Processing metric query_range-api-kas-request-duration-p99.json.gz ERRO[2025-02-04T21:44:16-03:00] no valid data for metric query_range-api-kas-request-duration-p99.json.gz DEBU[2025-02-04T21:44:16-03:00] Processing metric query_range-etcd-disk-fsync-wal-duration-p99.json.gz ERRO[2025-02-04T21:44:16-03:00] no valid data for metric query_range-etcd-disk-fsync-wal-duration-p99.json.gz DEBU[2025-02-04T21:44:16-03:00] Processing metric query_range-etcd-peer-round-trip-time.json.gz ERRO[2025-02-04T21:44:16-03:00] no valid data for metric query_range-etcd-peer-round-trip-time.json.gz ERRO[2025-02-04T21:44:16-03:00] empty metric data, ignoring metric query_range-cluster-cpu-usage.json.gz DEBU[2025-02-04T21:44:16-03:00] Processing metric query_range-etcd-disk-fsync-db-duration-p99.json.gz ERRO[2025-02-04T21:44:16-03:00] no valid data for metric query_range-etcd-disk-fsync-db-duration-p99.json.gz DEBU[2025-02-04T21:44:16-03:00] Processing metric query_range-etcd-total-leader-elections-day.json.gz ERRO[2025-02-04T21:44:16-03:00] no valid data for metric query_range-etcd-total-leader-elections-day.json.gz DEBU[2025-02-04T21:44:16-03:00] Processing metric query_range-etcd-request-duration-p99.json.gz ERRO[2025-02-04T21:44:16-03:00] no valid data for metric query_range-etcd-request-duration-p99.json.gz
Considering the metrics are something experimental, not required to raise attention to the reviewer, and not normalized the convention across different installations, we can convert the ERROR level to DEBUG, and if needed, open a new card to investigate if there are another evidence/reasons that log haven't been collected.