# Displaying number field in (K|M|G)bits/s

**URL:** <https://discuss.elastic.co/t/displaying-number-field-in-k-m-g-bits-s/230576>\
**Category:** Kibana\
**Created:** [April 30, 2020, 2:41pm UTC](https://discuss.elastic.co/t/displaying-number-field-in-k-m-g-bits-s/230576 "2020-04-30T14:41:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marko\_Todoric](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marko_todoric/32/52975_2.png) [@Marko\_Todoric](https://discuss.elastic.co/u/Marko_Todoric)\
**Post date:** [April 30, 2020, 2:41pm UTC](https://discuss.elastic.co/t/displaying-number-field-in-k-m-g-bits-s/230576/1 "2020-04-30T14:41:37Z")

</div>

Hello everyone.  
I want to measure hourly speedtest and keep that info and luckily, speedtest-cli app can output to json, which i can use to import to elasticsearch. Now, data displayed by speedtest-cli contains upload and download speed in bits, not bytes. I know that Kibana has a way to specify a field as "Bytes" and it will display number fields depending on bytes size. However, if i choose the "download" field which contains a number in bits, it will display that in bytes. It's like this.

```auto
{
  "download" : 58478385.98511417,
  "upload" : 7753314.934425002
}

```

When in Kibana i mark those number fields as "Bytes", it will display it like:

```auto
download: 55.8MB
upload: 7.4MB

```

when it should be:

```auto
download: 58.5
upload: 7.8

```

I mean, the calculation performed by kibana is just fine, it just calculates by using 1024 units instead of 1000 if bits are in play. How to achieve that if there is a way to make it work?

---

<div class="post-metadata">

**Author:** ![wylie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wylie/32/81794_2.png) [@wylie](https://discuss.elastic.co/u/wylie)\
**Post date:** [April 30, 2020, 2:54pm UTC](https://discuss.elastic.co/t/displaying-number-field-in-k-m-g-bits-s/230576/2 "2020-04-30T14:54:42Z")

</div>

In the upcoming 7.7.0 release, I introduced a set of new formatting options that will support bits and bytes with different decimal bases: [https://www.elastic.co/guide/en/kibana/7.7/numeral.html#\_bytes\_and\_bits](https://www.elastic.co/guide/en/kibana/7.7/numeral.html#_bytes_and_bits)

---

<div class="post-metadata">

**Author:** ![Marko\_Todoric](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marko_todoric/32/52975_2.png) [@Marko\_Todoric](https://discuss.elastic.co/u/Marko_Todoric)\
**Post date:** [April 30, 2020, 3:06pm UTC](https://discuss.elastic.co/t/displaying-number-field-in-k-m-g-bits-s/230576/3 "2020-04-30T15:06:57Z")

</div>

Niiiiiiice! Can't wait for 7.7 then. I'm currently on 7.6.2

---

<div class="post-metadata">

**Author:** ![wylie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wylie/32/81794_2.png) [@wylie](https://discuss.elastic.co/u/wylie)\
**Post date:** [April 30, 2020, 3:41pm UTC](https://discuss.elastic.co/t/displaying-number-field-in-k-m-g-bits-s/230576/4 "2020-04-30T15:41:52Z")

</div>

If you are interested in a workaround, some users who want to convert their numbers into a "per second" metric use the TSVB app. Here is a recent blog post about showing rates in TSVB: [https://www.elastic.co/blog/visualizing-observability-with-kibana-event-rates-and-rate-of-change-in-tsvb](https://www.elastic.co/blog/visualizing-observability-with-kibana-event-rates-and-rate-of-change-in-tsvb)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 28, 2020, 3:41pm UTC](https://discuss.elastic.co/t/displaying-number-field-in-k-m-g-bits-s/230576/5 "2020-05-28T15:41:59Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.