# Uptime 8.5 Not showing in Kibana

**URL:** https://discuss.elastic.co/t/uptime-8-5-not-showing-in-kibana/318758
**Category:** Synthetics
**Created:** [November 11, 2022, 6:11pm UTC](https://discuss.elastic.co/t/uptime-8-5-not-showing-in-kibana/318758 "2022-11-11T18:11:57Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![PublicName](https://avatars.discourse-cdn.com/v4/letter/p/74df32/32.png) [@PublicName](https://discuss.elastic.co/u/PublicName)
#### Post date: [November 11, 2022, 6:11pm UTC](https://discuss.elastic.co/t/uptime-8-5-not-showing-in-kibana/318758/1 "2022-11-11T18:11:57Z")

</div>

Kibana and Elastic version 8.5.

8.4.x all monitors where showing in Uptime in Kibana. Updated to 8.5 and now all are missing on several clusters all on 8.5. Checking the indices data is still being sent to ES as expected just the display output is empty. Briefly it will show if you restart Kibana but this is obviously a work around. No errors are showing in Kibana logs and Heartbeat is showing normal as well.

Browser cache was cleared and still same results. Any pointers to where to start looking? This is a critical function and a large part of what is used day to day.

---

<div class="post-metadata">

### Author: ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [November 11, 2022, 6:32pm UTC](https://discuss.elastic.co/t/uptime-8-5-not-showing-in-kibana/318758/2 "2022-11-11T18:32:47Z")

</div>

Perhaps this

> [@Heartbeat 8.5.0 mapper error workaround](https://discuss.elastic.co/t/heartbeat-8-5-0-mapper-error-workaround/318132):
>
> Hi all, Andrew from Elastic here, Tech Lead for Heartbeat. We're sorry to report that Heartbeat 8.5.0 has a severe bug that will break indexing in most installs after ~30m of runtime. The good news is there's an easy workaround that will fix it, detailed below. If you'd rather wait until Elastic Stack 8.5.1 is released that will also work. Read on for details. The error in question will look like the following in the Heartbeat logs: {..., "reason":"failed to parse date field [4.0614878e+07] wi…

---

<div class="post-metadata">

### Author: ![PublicName](https://avatars.discourse-cdn.com/v4/letter/p/74df32/32.png) [@PublicName](https://discuss.elastic.co/u/PublicName)
#### Post date: [November 11, 2022, 7:02pm UTC](https://discuss.elastic.co/t/uptime-8-5-not-showing-in-kibana/318758/3 "2022-11-11T19:02:13Z")

</div>

You are awesome thank you much for the quick fix. My search skills are off this day...

Tested on 2 clusters and both so far have been working as expected.

---

<div class="post-metadata">

### Author: ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [November 17, 2022, 5:40am UTC](https://discuss.elastic.co/t/uptime-8-5-not-showing-in-kibana/318758/4 "2022-11-17T05:40:34Z")

</div>

@PublicName I think 8.5.1 is out... FYI

---

<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 11, 2022, 5:41am UTC](https://discuss.elastic.co/t/uptime-8-5-not-showing-in-kibana/318758/5 "2022-12-11T05:41:32Z")

</div>

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