# Why Interval in Visualization by Auto is per 0 milliseconds

**URL:** <https://discuss.elastic.co/t/why-interval-in-visualization-by-auto-is-per-0-milliseconds/157333>\
**Category:** Kibana\
**Created:** [November 19, 2018, 11:04am UTC](https://discuss.elastic.co/t/why-interval-in-visualization-by-auto-is-per-0-milliseconds/157333 "2018-11-19T11:04:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![\_Sergey](https://avatars.discourse-cdn.com/v4/letter/_/e68b1a/32.png) [@\_Sergey](https://discuss.elastic.co/u/_Sergey)\
**Post date:** [November 19, 2018, 11:04am UTC](https://discuss.elastic.co/t/why-interval-in-visualization-by-auto-is-per-0-milliseconds/157333/1 "2018-11-19T11:04:03Z")

</div>

Hey guys,

We faced with issue that suddenly all our visualizations (line, bar chars) have X-axis (using Date histogram) split by Auto per milliseconds 0. Previously we use this Auto feature and since you change time period of visualization/dashboard it shows/changes to proper interval (if interval 7+ days, it shows split per day, or 3 hours which is very readable).  
Once this feature is changed (don't know why), not after update of Kibana, by Auto always show Interval per 0 millisec.  
So where it is possible to check settings to change this behavior?

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/b/3b01864e78077d4fa4c09ab5cc8fb5d150d6b5a7.png)  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/8/2/82ad83bb4fb3dc8b7e35159c33d7c81425e860a6.png)

---

<div class="post-metadata">

**Author:** ![thomasneirynck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomasneirynck/32/23313_2.png) [@thomasneirynck](https://discuss.elastic.co/u/thomasneirynck)\
**Post date:** [November 19, 2018, 8:02pm UTC](https://discuss.elastic.co/t/why-interval-in-visualization-by-auto-is-per-0-milliseconds/157333/2 "2018-11-19T20:02:30Z")

</div>

@_Sergey

it seems Kibana is trying to do some form of auto-correction. when you see that warning message `this interval creates too many buckets ...`

It doesn't explain exactly why it shows by 0-milliseconds, but this is likely due to some rounding error.

If you open the spy-panel and look at the ES-request, what is the interval that the data is requested on?

---

<div class="post-metadata">

**Author:** ![\_Sergey](https://avatars.discourse-cdn.com/v4/letter/_/e68b1a/32.png) [@\_Sergey](https://discuss.elastic.co/u/_Sergey)\
**Post date:** [November 20, 2018, 9:27am UTC](https://discuss.elastic.co/t/why-interval-in-visualization-by-auto-is-per-0-milliseconds/157333/3 "2018-11-20T09:27:24Z")

</div>

Hi Thomas,

As I checked it has next:

```
{
  "aggs": {
    "2": {
      "date_histogram": {
        "field": "@timestamp",
        "interval": "5s",
        "time_zone": "UTC",
        "min_doc_count": 1
      }
```

---

<div class="post-metadata">

**Author:** ![\_Sergey](https://avatars.discourse-cdn.com/v4/letter/_/e68b1a/32.png) [@\_Sergey](https://discuss.elastic.co/u/_Sergey)\
**Post date:** [November 20, 2018, 9:37am UTC](https://discuss.elastic.co/t/why-interval-in-visualization-by-auto-is-per-0-milliseconds/157333/4 "2018-11-20T09:37:39Z")

</div>

Hey,  
Just figure out what was the reason:

As we have prod and stag Kibana, I think to check advance settings in Index Patterns (as on Stag we don't have this issue with Auto interval 0 millisec).

So I find out that somebody changed this settings (it was a blank space before 1000):

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/a/3a8a34d2a46085fe2c3324d29e6a655047127474.png)

Once I changed it (delete that blank space) and check our graphs - all back to normal. No Auto generates (depends on time period of check) readable intervals.

---

<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:** [December 18, 2018, 9:37am UTC](https://discuss.elastic.co/t/why-interval-in-visualization-by-auto-is-per-0-milliseconds/157333/5 "2018-12-18T09:37:46Z")

</div>

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