# Kibana monitoring - recent log entries lost timezone

**URL:** <https://discuss.elastic.co/t/kibana-monitoring-recent-log-entries-lost-timezone/217889>\
**Category:** Kibana\
**Tags:** elastic-stack-monitoring\
**Created:** [February 4, 2020, 10:38pm UTC](https://discuss.elastic.co/t/kibana-monitoring-recent-log-entries-lost-timezone/217889 "2020-02-04T22:38:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\
**Post date:** [February 4, 2020, 10:38pm UTC](https://discuss.elastic.co/t/kibana-monitoring-recent-log-entries-lost-timezone/217889/1 "2020-02-04T22:38:45Z")

</div>

Just noticed that on the Monitoring overview screen, "recent log entries" have the wrong timestamp by our timezone offset. The same log entry in Discover has the correct timestamp.

Everything involved is 7.5.2, filebeat elasticsearch module sending to elastic ingest pipeline, all are pretty basic config. We don't really use the monitoring log entries screen, it's easier to search in discover, but it causes a brief panic.

Any ideas?

Thanks.

---

<div class="post-metadata">

**Author:** ![Igor\_Zaytsev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_zaytsev/32/50662_2.png) [@Igor\_Zaytsev](https://discuss.elastic.co/u/Igor_Zaytsev)\
**Post date:** [February 5, 2020, 5:57pm UTC](https://discuss.elastic.co/t/kibana-monitoring-recent-log-entries-lost-timezone/217889/2 "2020-02-05T17:57:48Z")

</div>

Hey @rugenl,

I was wondering if the offset is still correct based on the "dateFormat:tz" you have set in Kibana \> Management \> Advanced settings?

If you have it set to Browser, then it should apply the offset based on your current location. Discover might be using UTC, so you can also try setting that offset to match the data.

Also, do you see any GMT offset in the url, when you change the timeframe?

---

<div class="post-metadata">

**Author:** ![Igor\_Zaytsev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_zaytsev/32/50662_2.png) [@Igor\_Zaytsev](https://discuss.elastic.co/u/Igor_Zaytsev)\
**Post date:** [February 5, 2020, 7:53pm UTC](https://discuss.elastic.co/t/kibana-monitoring-recent-log-entries-lost-timezone/217889/3 "2020-02-05T19:53:47Z")

</div>

@rugenl

Disregard my previous post. We have identified that this is indeed a bug on our end: [https://github.com/elastic/kibana/issues/56903](https://github.com/elastic/kibana/issues/56903)

Thank you for bringing it to our attention!

---

<div class="post-metadata">

**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\
**Post date:** [February 5, 2020, 8:06pm UTC](https://discuss.elastic.co/t/kibana-monitoring-recent-log-entries-lost-timezone/217889/4 "2020-02-05T20:06:08Z")

</div>

Opened 42 minutes ago, I got a fresh one 🙂

Thanks

---

<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:** [March 4, 2020, 8:06pm UTC](https://discuss.elastic.co/t/kibana-monitoring-recent-log-entries-lost-timezone/217889/5 "2020-03-04T20:06:20Z")

</div>

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