# 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:** 1
**Showing post:** 2

<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…

---

_[View the full topic](https://discuss.elastic.co/t/uptime-8-5-not-showing-in-kibana/318758)._