Hello,
We’ve noticed that the current output for table bloat metrics displays values with excessive decimal precision, which makes it harder to read and interpret quickly in monitoring tools.
For example, the output currently looks like:
schema_name.table_name 12.2350387573242GB / 24.4807739257812GB (49.98%)
This level of precision is not particularly useful in an operational context and adds visual noise.
Expected behavior:
It would be more readable and practical to limit the precision to 2 decimal places, for example:
schema_name.table_name 12.23GB / 24.48GB (49.98%)
Why this matters:
Improves readability in dashboards and alerts
Makes logs easier to scan quickly during incidents
Aligns with common practices for displaying storage sizes
Suggested improvement:
Round or format size values (in GB) to a fixed precision (e.g., 2 decimal places) before displaying them.
If needed, higher precision could optionally be exposed via a verbose/debug mode.
Thanks!
Hello,
We’ve noticed that the current output for table bloat metrics displays values with excessive decimal precision, which makes it harder to read and interpret quickly in monitoring tools.
For example, the output currently looks like:
schema_name.table_name 12.2350387573242GB / 24.4807739257812GB (49.98%)
This level of precision is not particularly useful in an operational context and adds visual noise.
Expected behavior:
It would be more readable and practical to limit the precision to 2 decimal places, for example:
schema_name.table_name 12.23GB / 24.48GB (49.98%)
Why this matters:
Improves readability in dashboards and alerts
Makes logs easier to scan quickly during incidents
Aligns with common practices for displaying storage sizes
Suggested improvement:
Round or format size values (in GB) to a fixed precision (e.g., 2 decimal places) before displaying them.
If needed, higher precision could optionally be exposed via a verbose/debug mode.
Thanks!