Bug 1634299 - Humanize KubePersistentVolumeFullInFourDays annotation
Summary: Humanize KubePersistentVolumeFullInFourDays annotation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.1.0
Assignee: Frederic Branczyk
QA Contact: Junqi Zhao
URL:
Whiteboard: 4.1.2
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-29 15:37 UTC by Justin Pierce
Modified: 2019-06-19 06:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-19 06:45:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:1382 0 None None None 2019-06-19 06:45:44 UTC

Description Justin Pierce 2018-09-29 15:37:59 UTC
Description of problem:
The messages for KubePersistentVolumeFullInFourDays include non-humanized bytes counts:

>>>>
Based on recent sampling, the persistent volume claimed by php-storage in namespace kube-system is expected to fill up within four days. Currently 6.0686336e+07 bytes are available.
<<<<

Current message: "Based on recent sampling, the persistent volume claimed by {{ $labels.persistentvolumeclaim
    }} in namespace {{ $labels.namespace }} is expected to fill up within four days.
    Currently {{ $value }} bytes are available."

Piping through humanize1024 should improve usability. 

Version-Release number of selected component (if applicable):
v.3.11.16

How reproducible:
100%


Expected results:
Should MB/GB/etc would be more effective than scientific notation. 

Additional info:
Noticed in KubePersistentVolumeFullInFourDays, but there may be more messages which could use this.

Comment 1 minden 2018-10-01 12:16:19 UTC
Great idea Justin. Thanks. Tracked here: https://github.com/kubernetes-monitoring/kubernetes-mixin/issues/100

Comment 3 Frederic Branczyk 2019-06-05 14:46:01 UTC
This has been released as part of 4.1.

Comment 7 errata-xmlrpc 2019-06-19 06:45:34 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, 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-2019:1382


Note You need to log in before you can comment on or make changes to this bug.