# Uptime Tab says "No Data Available" when heartbeat-today index keeps incrementing

**URL:** https://discuss.elastic.co/t/uptime-tab-says-no-data-available-when-heartbeat-today-index-keeps-incrementing/179160
**Category:** Synthetics
**Created:** [April 30, 2019, 10:54pm UTC](https://discuss.elastic.co/t/uptime-tab-says-no-data-available-when-heartbeat-today-index-keeps-incrementing/179160 "2019-04-30T22:54:55Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![phillhocking](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phillhocking/32/45351_2.png) [@phillhocking](https://discuss.elastic.co/u/phillhocking)
#### Post date: [April 30, 2019, 10:54pm UTC](https://discuss.elastic.co/t/uptime-tab-says-no-data-available-when-heartbeat-today-index-keeps-incrementing/179160/1 "2019-04-30T22:54:55Z")

</div>

Hi Elastic friends! My Uptime app tab says "No uptime data available -  
Configure Heartbeat to start logging uptime data" but I have verified that heartbeat is shipping data at least according to \_cat/indices:

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

It does appear like the uptime data is getting populated and logs on the machine that heartbeat is running on suggests that the data is being shipped, but Uptime doesn't seem to be getting the memo. What am I missing?

---

<div class="post-metadata">

### Author: ![phillhocking](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phillhocking/32/45351_2.png) [@phillhocking](https://discuss.elastic.co/u/phillhocking)
#### Post date: [May 1, 2019, 6:03am UTC](https://discuss.elastic.co/t/uptime-tab-says-no-data-available-when-heartbeat-today-index-keeps-incrementing/179160/2 "2019-05-01T06:03:14Z")

</div>

Everything is 7.0 and a fresh install, but I noticed this while reviewing the documentation:

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

It does appear that my index that is automatically created is actually `heartbeat-date` not `heartbeat-7-date`. Could this possibly be what is giving me the trouble? I look forward to feedback! 😃

---

<div class="post-metadata">

### Author: ![phillhocking](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phillhocking/32/45351_2.png) [@phillhocking](https://discuss.elastic.co/u/phillhocking)
#### Post date: [May 1, 2019, 7:12am UTC](https://discuss.elastic.co/t/uptime-tab-says-no-data-available-when-heartbeat-today-index-keeps-incrementing/179160/3 "2019-05-01T07:12:46Z")

</div>

Hey @warkolm I figured it out! I just had to change these fields in my config and kick it over. Here was the error condition:

`setup.ilm.rollover_alias: "heartbeat-"`  
`setup.ilm.pattern: "{now/d}-000001"`

And this was the remedy:

`setup.ilm.rollover_alias: "heartbeat-7.0.0"`  
`setup.ilm.pattern: "{now/d}-000001"`

I'm sure glad I figured this out just by poking around and reading the manual. I hope this is helpful to someone else experiencing a similar issue! 😅

---

<div class="post-metadata">

### Author: ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [May 1, 2019, 3:31pm UTC](https://discuss.elastic.co/t/uptime-tab-says-no-data-available-when-heartbeat-today-index-keeps-incrementing/179160/4 "2019-05-01T15:31:18Z")

</div>

@phillhocking just to make sure we're not missing anything here, the root cause seems to have been a misconfiguration of `setup.ilm.rollover_alias` right? The default values are fine AFAICT right? I tried to repro but didn't get this issue on a fresh install myself.

---

<div class="post-metadata">

### Author: ![phillhocking](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phillhocking/32/45351_2.png) [@phillhocking](https://discuss.elastic.co/u/phillhocking)
#### Post date: [May 1, 2019, 5:11pm UTC](https://discuss.elastic.co/t/uptime-tab-says-no-data-available-when-heartbeat-today-index-keeps-incrementing/179160/5 "2019-05-01T17:11:45Z")

</div>

Hey, @Andrew_Cholakian1 thanks for checking in! Indeed, I had a misconfiguration and as far as I know - the defaults are fine. I am relatively new to managing and configuring the Elastic stack and made an elementary mistake. Thank you so much for your reply and diligence doing a repro!

---

<div class="post-metadata">

### Author: ![phillhocking](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phillhocking/32/45351_2.png) [@phillhocking](https://discuss.elastic.co/u/phillhocking)
#### Post date: [May 16, 2019, 5:10am UTC](https://discuss.elastic.co/t/uptime-tab-says-no-data-available-when-heartbeat-today-index-keeps-incrementing/179160/6 "2019-05-16T05:10:28Z")

</div>

I just wanted you all to know that everything is chugging along great since 7.0.1. Thank you all for your unceasing efforts! 😃

---

<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: [June 9, 2019, 5:10am UTC](https://discuss.elastic.co/t/uptime-tab-says-no-data-available-when-heartbeat-today-index-keeps-incrementing/179160/7 "2019-06-09T05:10:30Z")

</div>

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