# Uptime does not display the details accurately **URL:** \ **Category:** Synthetics\ **Created:** [October 10, 2022, 11:43am UTC](https://discuss.elastic.co/t/uptime-does-not-display-the-details-accurately/316214 "2022-10-10T11:43:48Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![swchandu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swchandu/32/95295_2.png) [@swchandu](https://discuss.elastic.co/u/swchandu)\ **Post date:** [October 10, 2022, 11:43am UTC](https://discuss.elastic.co/t/uptime-does-not-display-the-details-accurately/316214/1 "2022-10-10T11:43:48Z")
Hi, ELK 8.4.1 does not show correct details in uptime home. The graph is blank and monitors does not show correct time. But I can go through the monitor and check latest steps's data by clicking on next Did any one faced this/know how to fix it? ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/d/ad32697814f070bcfe903d65fa956b97df1f5068.png) ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/6/560419cb15c2e6d19e700aee4922a42cb93196a3.png) ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/3/7310e83d47254586dc362fa95a1b89707fa65388.png) Thanks ---
**Author:** ![jkambic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jkambic/32/53306_2.png) [@jkambic](https://discuss.elastic.co/u/jkambic)\ **Post date:** [October 10, 2022, 1:46pm UTC](https://discuss.elastic.co/t/uptime-does-not-display-the-details-accurately/316214/2 "2022-10-10T13:46:06Z")
Hi @swchandu sorry you're having some issues with Uptime. A few initial questions that might help us diagnose the problem: - Are using Logstash to ingest your data to Uptime? - Are you running an on-prem deployment, or using Elastic Cloud? - Are you able to see any errors in your browser's network tab or in the browser console? ---
**Author:** ![swchandu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swchandu/32/95295_2.png) [@swchandu](https://discuss.elastic.co/u/swchandu)\ **Post date:** [October 10, 2022, 2:23pm UTC](https://discuss.elastic.co/t/uptime-does-not-display-the-details-accurately/316214/3 "2022-10-10T14:23:07Z")
I am using on-prem and no Logstash. All the steps are running fine. it is only not being displayed in the uptime app. If I am going through the monitor instance, It is providing the next to view latest details. But the issue is with the uptime home page which does nto show correct details. ---
**Author:** ![jkambic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jkambic/32/53306_2.png) [@jkambic](https://discuss.elastic.co/u/jkambic)\ **Post date:** [October 10, 2022, 2:56pm UTC](https://discuss.elastic.co/t/uptime-does-not-display-the-details-accurately/316214/4 "2022-10-10T14:56:58Z")
Thanks for confirming those details. How are your monitors defined and managed? Are you using Monitor Management in the Uptime UI, Fleet, local config with Heartbeat/Docker, etc.? ---
**Author:** ![swchandu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swchandu/32/95295_2.png) [@swchandu](https://discuss.elastic.co/u/swchandu)\ **Post date:** [October 10, 2022, 3:13pm UTC](https://discuss.elastic.co/t/uptime-does-not-display-the-details-accurately/316214/5 "2022-10-10T15:13:05Z")
I am using heartbeat 8.4.1 docker container and monitors are written in playwright inline steps on local heartbeat.yml. This is directly connecting to elasticsearch 8.4.1 (docker version) Fleet not used. ---
**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:** [October 10, 2022, 4:44pm UTC](https://discuss.elastic.co/t/uptime-does-not-display-the-details-accurately/316214/6 "2022-10-10T16:44:37Z")
I think this can happens if there is clock difference between where your heartbeat is running vs kibana machine? Can you please make sure those are in sync. we are trying to investigate if it could be something else. ---
**Author:** ![jkambic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jkambic/32/53306_2.png) [@jkambic](https://discuss.elastic.co/u/jkambic)\ **Post date:** [October 10, 2022, 4:55pm UTC](https://discuss.elastic.co/t/uptime-does-not-display-the-details-accurately/316214/7 "2022-10-10T16:55:03Z")
As @shahzad31 mentioned - if the system clocks are too far out of sync between the HB container and Kibana/ES server it can cause some of the queries to not work properly, which could be the reason you're not seeing anything in the histogram (and perhaps incorrect time on the monitors you are seeing). I've verified the histogram worked using a basic config like the one below against ES 8.4.1 and the matching Heartbeat Docker image. It does not seem like a configuration issue is the cause of your problem though, as most of the functionality is working. ```auto output.elasticsearch: username: elastic password: changeme hosts: ['http://host.docker.internal:9200'] heartbeat.monitors: - type: browser id: synthetic-inline-tests name: Elastic website schedule: '@every 1m' source: inline: script: |- step("load homepage", async () => { await page.goto('https://www.elastic.co'); }); step("hover over products menu", async () => { await page.hover('css=[data-nav-item=products]'); }); ``` ---
**Author:** ![swchandu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swchandu/32/95295_2.png) [@swchandu](https://discuss.elastic.co/u/swchandu)\ **Post date:** [October 12, 2022, 6:49pm UTC](https://discuss.elastic.co/t/uptime-does-not-display-the-details-accurately/316214/8 "2022-10-12T18:49:26Z")
> [@jkambic](#): > > As @shahzad31 mentioned - if the system clocks are too far out of sync between the HB container and Kibana/ES server it can cause some of the queries to not work properly, which could be the reason you're not seeing anything in the histogram (and perhaps incorrect time on the monitors you are seeing). You are right. I have just noticed that heartbeat's server time is ahead. I have fixed it. However, the same issue continues. ---
**Author:** ![jkambic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jkambic/32/53306_2.png) [@jkambic](https://discuss.elastic.co/u/jkambic)\ **Post date:** [October 17, 2022, 1:53pm UTC](https://discuss.elastic.co/t/uptime-does-not-display-the-details-accurately/316214/9 "2022-10-17T13:53:17Z")
Hi @swchandu - are you still facing this problem? One other thing worth trying here would be to stop Heartbeat and either: - delete the index - configure Heartbeat to write to a new index Then, restart the agent. If you configured it to write to a new index, make sure you [update the pattern](https://www.elastic.co/guide/en/observability/current/configure-uptime-settings.html#configure-uptime-indices) in Uptime settings. It's possible that the mapping could be incorrect for your index, which has caused similar issues in the past. ---
**Author:** ![swchandu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swchandu/32/95295_2.png) [@swchandu](https://discuss.elastic.co/u/swchandu)\ **Post date:** [October 17, 2022, 3:09pm UTC](https://discuss.elastic.co/t/uptime-does-not-display-the-details-accurately/316214/10 "2022-10-17T15:09:25Z")
> [@jkambic](#): > > ew index, make sure you [update the pattern](https://www.elastic.co/guide/en/observability/current/configure-uptime-settings.html#configure-uptime-indices) in Uptime settings. It's possible that the mapping could be incorrect for your index, which has caused similar issues in the past. Thanks. It worked ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 10, 2022, 3:09pm UTC](https://discuss.elastic.co/t/uptime-does-not-display-the-details-accurately/316214/11 "2022-11-10T15:09:42Z")
This topic was automatically closed 24 days after the last reply. New replies are no longer allowed.