# Infrastructure graph period cannot display less than 1m period

**URL:** <https://discuss.elastic.co/t/infrastructure-graph-period-cannot-display-less-than-1m-period/172194>\
**Category:** Kibana\
**Created:** [March 13, 2019, 5:25pm UTC](https://discuss.elastic.co/t/infrastructure-graph-period-cannot-display-less-than-1m-period/172194 "2019-03-13T17:25:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamesdh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesdh/32/41929_2.png) [@jamesdh](https://discuss.elastic.co/u/jamesdh)\
**Post date:** [March 13, 2019, 5:25pm UTC](https://discuss.elastic.co/t/infrastructure-graph-period-cannot-display-less-than-1m-period/172194/1 "2019-03-13T17:25:24Z")

</div>

Using latest Kibana 7.0.0-beta1 along with Metricbeat, the graph visualizations when viewing metrics under Infrastructure cannot be shown with an interval of less than 1m. I've configured my Metricbeats to use a period of 10s, and have verified that the events appear in the index every 10s by doing a quick search under Discover.

The graph is rendered with intervals of 15s, which is what I'd like to see. Is there any way to configure this so that it actually uses the data we are submitting to it?

 ![14%20PM](https://us1.discourse-cdn.com/elastic/original/3X/3/d/3dda5a70296edad6edfc83eb10e07ad785ad46d3.png)

---

<div class="post-metadata">

**Author:** ![cufflinks](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cufflinks/32/42129_2.png) [@cufflinks](https://discuss.elastic.co/u/cufflinks)\
**Post date:** [March 13, 2019, 10:23pm UTC](https://discuss.elastic.co/t/infrastructure-graph-period-cannot-display-less-than-1m-period/172194/2 "2019-03-13T22:23:00Z")

</div>

I have pinged members of the infrastructure team and will respond once they let me know how we can achieve this.

---

<div class="post-metadata">

**Author:** ![cufflinks](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cufflinks/32/42129_2.png) [@cufflinks](https://discuss.elastic.co/u/cufflinks)\
**Post date:** [March 14, 2019, 12:06am UTC](https://discuss.elastic.co/t/infrastructure-graph-period-cannot-display-less-than-1m-period/172194/3 "2019-03-14T00:06:38Z")

</div>

Hello James,

Unfortunately, there is no way to adjust that interval. Per the infrastructure team,

```auto
Lower intervals would be way too susceptible to the jitter of the document submission
and some metrics like I/O rates are derivatives that need to be calculated across multiple buckets.
For that reason, getting the metrics out of elasticsearch 1:1 is very difficult since they're always part of an aggregation.

```

I hope this helps.

---

<div class="post-metadata">

**Author:** ![jamesdh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesdh/32/41929_2.png) [@jamesdh](https://discuss.elastic.co/u/jamesdh)\
**Post date:** [March 14, 2019, 2:46pm UTC](https://discuss.elastic.co/t/infrastructure-graph-period-cannot-display-less-than-1m-period/172194/4 "2019-03-14T14:46:32Z")

</div>

Thanks John for the quick response!

---

<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:** [April 11, 2019, 2:46pm UTC](https://discuss.elastic.co/t/infrastructure-graph-period-cannot-display-less-than-1m-period/172194/5 "2019-04-11T14:46:36Z")

</div>

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