Reveal the real/raw count on rounded/abbreviated values

[igoristic]

It might be a bit confusing with realtime rounded/abbreviated numbers sometimes, since the raw value changes, but the rounded UI value stays the same. It becomes harder to see the real number as it grows, especially when it reaches millions eg: 1,560,001, 1,600,000 and 1,640,990 will all still be displayed as 1.6m when looking at Stack Monitoring > Overview summary info cards:

Couple of proposed solutions:

• Reveal the real value as a tooltip when hovering over the rounded number
• Show the real value as a smaller/lighter number below the rounded number

[elasticmachine]

Pinging @elastic/kibana-design

[elasticmachine]

Pinging @elastic/stack-monitoring

[cchaos]

A simple solution could be just adding another digit to your decimal point. Like: 1.75k vs 1.67k and 1.56M vs 1.64M

[ycombinator]

@cchaos That would help the issue a little bit but it would still be an issue for slow-changing values.

[cchaos]

If it's that important to see the full number, then you probably should just show the full number?

[ycombinator]

@cchaos I don't know if that will be possible in every place we're using rounding but certainly for the two numbers shown in the screenshot above, we have enough space to show the entire numbers and should probably just do that.

[chrisronline]

WYDT about this approach:

• Use the full number
• Use .eui-textTruncate for all the text
• Add tooltips that show the full number in case the text is suppressed

[cachedout]

As I've mentioned in another PR, I am way about displaying data in tooltips because it makes it hard to screenshot it, but in this case since we're only doing it if it would otherwise be suppressed, I think we're OK. 👍

[cchaos]

I'd be concerned about truncating large numbers. For example if the full number is 1,234,567,890 and you truncate to 1,234... There's no way to know how many more digits come after that. However if you summarize that number as 1.234 B (billion) that's a lot more accurate.

[chrisronline]

There's no way to know how many more digits come after that.

Wouldn't that be the point of the tooltip? That would show the full number. The user would know the number has been truncated (because of ...) and they'd mouse over to see the full number (if interested)

[cchaos]

Right, but at a glance you might look at something like:

1,234...                      234...                      23,4...

And have no idea how much more number there is after that. The user then has to hover over each value read it, remember it, then hover the next to parse the differences. It would be much easier to read at a glance:

1.234 B                      234 K                      23.4 M

And understand both scale and relativity.

You can still use tooltips to display the full number, but this gives you a more accurate representation of the full number in a summarized way.

[cchaos]

The original approach is good, I think you just need to add those tooltips for the full number and maybe increase your decimal points to 2 or 3.