# Weird Uptime Data Visualization

**URL:** <https://discuss.elastic.co/t/weird-uptime-data-visualization/269181>\
**Category:** Synthetics\
**Created:** [April 4, 2021, 12:46pm UTC](https://discuss.elastic.co/t/weird-uptime-data-visualization/269181 "2021-04-04T12:46:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![GeekyAle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/geekyale/32/86542_2.png) [@GeekyAle](https://discuss.elastic.co/u/GeekyAle)\
**Post date:** [April 4, 2021, 12:46pm UTC](https://discuss.elastic.co/t/weird-uptime-data-visualization/269181/1 "2021-04-04T12:46:02Z")

</div>

Hello Everyone,

As per the title, I'm having a strange visualization of the Uptime data,

I have Heartbeat monitoring 7 hosts in my house, and the monitor is set to every 30sec.

Now to the weirdness; With the monitor every 30sec, if I set the Date Picker to `Last 15 Minutes`, I see that every 5th hits, regularly, it shows the bars doubled (14 hits), like it's reading the data twice:

 ![Schermata 2021-04-04 alle 14.27.05](https://us1.discourse-cdn.com/elastic/original/3X/1/d/1d03afc6557daf88cf85adfe7709258c52d33137.png)

I get to see a consistent data set with `Last 750 seconds` (with every bars counting 7 hits, correctly):

 ![Schermata 2021-04-04 alle 14.27.18](https://us1.discourse-cdn.com/elastic/original/3X/1/6/16f9e67e22262e3fec4f69bb95d3e705d2685628.png)

Before changing to 30sec, I had the Heartbeat ping every 1min and where it now shows the bar doubled, I used to have a "hole" like no data was read.

Either in the Discover tab and in a custom Dashboard I tried to build to prove the data were good, I can see all the entries are pushed correctly every 30 seconds, with no duplicates and I get to see a constant, thus correct, number of hosts (7).

Here's a screenshot of my custom built Dashboard

_No in the pic, but the Date Picker here is set to `Last 15 Minutes` with a Refresh `every 60 seconds` just like the Default settings for the Uptime App Dashboard._

 ![Schermata 2021-04-04 alle 17.22.54](https://us1.discourse-cdn.com/elastic/original/3X/6/1/611a36eaed70a9c4c121acf27ac1b99ac1701a45.png)

Is there a way, on my side, to fix this weird behavior?

Thanks in advance! 😁

* * *

Elasticsearch version: **7.12.0**  
Kibana version: **7.12.0**  
Heartbeat version: **7.12.0**

---

<div class="post-metadata">

**Author:** ![shahzad31](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shahzad31/32/51637_2.png) [@shahzad31](https://discuss.elastic.co/u/shahzad31)\
**Post date:** [April 4, 2021, 10:24pm UTC](https://discuss.elastic.co/t/weird-uptime-data-visualization/269181/2 "2021-04-04T22:24:56Z")

</div>

@GeekyAle Welcome to the Elastic Discuss forum.

The problem you are facing is actually a bug in the query we fixed recently. [[Uptime] Update query for ping histogram by shahzad31 · Pull Request #95495 · elastic/kibana · GitHub](https://github.com/elastic/kibana/pull/95495)

It will be shipped with next release 7.12.1.

Regards

---

<div class="post-metadata">

**Author:** ![GeekyAle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/geekyale/32/86542_2.png) [@GeekyAle](https://discuss.elastic.co/u/GeekyAle)\
**Post date:** [April 4, 2021, 10:36pm UTC](https://discuss.elastic.co/t/weird-uptime-data-visualization/269181/3 "2021-04-04T22:36:44Z")

</div>

Great, thank you! 😁

---

<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 28, 2021, 10:37pm UTC](https://discuss.elastic.co/t/weird-uptime-data-visualization/269181/4 "2021-04-28T22:37:29Z")

</div>

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