# Visualized precision doesn't match field precision **URL:** \ **Category:** Kibana\ **Created:** [August 13, 2015, 6:24am UTC](https://discuss.elastic.co/t/visualized-precision-doesnt-match-field-precision/27299 "2015-08-13T06:24:52Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![hughesm02](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hughesm02/32/4167_2.png) [@hughesm02](https://discuss.elastic.co/u/hughesm02)\ **Post date:** [August 13, 2015, 6:24am UTC](https://discuss.elastic.co/t/visualized-precision-doesnt-match-field-precision/27299/1 "2015-08-13T06:24:52Z")
I have a field that I'd like to visualize to 3 decimal points. In Settings\>Indices I set the format of the field to "Number" with the default format "0,0.[000]". ![](https://us1.discourse-cdn.com/elastic/original/2X/2/2802f7b4d6e9f2f4bd122744962583ceb59f3ae8.PNG) In Discover I see the events to the expected precision and format. ![](https://us1.discourse-cdn.com/elastic/original/2X/b/ba7ddf418e654c26193a504249b47e0397c8d435.PNG) However, when I create a line visualization, the precision is lost and the integer value is used. ![](https://us1.discourse-cdn.com/elastic/original/2X/f/f41e3c9146bec8e85a38f2aaa3bf6efe443ec99d.PNG) How do I get the expected precision in my visualization? ---
**Author:** ![spalger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spalger/32/14092_2.png) [@spalger](https://discuss.elastic.co/u/spalger)\ **Post date:** [August 13, 2015, 5:03pm UTC](https://discuss.elastic.co/t/visualized-precision-doesnt-match-field-precision/27299/2 "2015-08-13T17:03:18Z")
This sounds like a bug to me, but I can't reproduce it in the latest versions of Kibana so it may have been fixed already. What version of Kibana are you using? ---
**Author:** ![spalger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spalger/32/14092_2.png) [@spalger](https://discuss.elastic.co/u/spalger)\ **Post date:** [August 13, 2015, 5:06pm UTC](https://discuss.elastic.co/t/visualized-precision-doesnt-match-field-precision/27299/3 "2015-08-13T17:06:45Z")
Could you also export the raw data for the visualization in question? Just click the little ![](https://us1.discourse-cdn.com/elastic/original/2X/a/a002f57d3efbe7bd72b29724c4eae075e4d8d781.png) at the bottom of the visualization and click the ![](https://us1.discourse-cdn.com/elastic/original/2X/a/aa7a15af2000da3522fcc29d12080108abed45df.png) link under the table. ---
**Author:** ![hughesm02](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hughesm02/32/4167_2.png) [@hughesm02](https://discuss.elastic.co/u/hughesm02)\ **Post date:** [August 13, 2015, 5:33pm UTC](https://discuss.elastic.co/t/visualized-precision-doesnt-match-field-precision/27299/4 "2015-08-13T17:33:17Z")
Hi Spencer, thanks for the reply. I'm using kibana 4.1.1. I've [exported](https://gist.github.com/hughes/2ceabe24d66a3a8fecab) the raw table data, as well as the request/response json when viewing data in the discover tab. ---
**Author:** ![hughesm02](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hughesm02/32/4167_2.png) [@hughesm02](https://discuss.elastic.co/u/hughesm02)\ **Post date:** [August 14, 2015, 2:55am UTC](https://discuss.elastic.co/t/visualized-precision-doesnt-match-field-precision/27299/5 "2015-08-14T02:55:47Z")
Okay, this is very strange. Starting at exactly 5pm pacific today, the visualization suddenly started showing the expected precision. I didn't even touch the system that's logging this data today, and previously logged values still show clamped to (mostly) integers. ![](https://us1.discourse-cdn.com/elastic/original/2X/0/01b6833a14a655fc5d8b7ebce305b5977b4cbf75.PNG) No idea what happened, but it's working now so I guess things are okay? ---
**Author:** ![hughesm02](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hughesm02/32/4167_2.png) [@hughesm02](https://discuss.elastic.co/u/hughesm02)\ **Post date:** [August 17, 2015, 9:34pm UTC](https://discuss.elastic.co/t/visualized-precision-doesnt-match-field-precision/27299/6 "2015-08-17T21:34:56Z")
Something about 5pm pacific is causing very strange behavior. Yesterday at exactly 5pm the aggregation switched back to clamping to integer values despite high-precision data in the individual events. Just noticed 5pm pacific = midnight UTC, which seems more relevant. ![](https://us1.discourse-cdn.com/elastic/original/2X/4/48060e02b060a43deb28d5c915f9a465b8fa10b9.png) ---
**Author:** ![tbragin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tbragin/32/45166_2.png) [@tbragin](https://discuss.elastic.co/u/tbragin)\ **Post date:** [August 18, 2015, 3:58pm UTC](https://discuss.elastic.co/t/visualized-precision-doesnt-match-field-precision/27299/7 "2015-08-18T15:58:37Z")
How are you ingesting the data? If Logstash, any parse errors in the logs around that time frame? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:14pm UTC](https://discuss.elastic.co/t/visualized-precision-doesnt-match-field-precision/27299/8 "2017-07-06T14:14:39Z")