# ELK - custom time

**URL:** https://discuss.elastic.co/t/elk-custom-time/256004
**Category:** Kibana
**Created:** [November 19, 2020, 2:39pm UTC](https://discuss.elastic.co/t/elk-custom-time/256004 "2020-11-19T14:39:51Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![raj.speed1](https://avatars.discourse-cdn.com/v4/letter/r/848f3c/32.png) [@raj.speed1](https://discuss.elastic.co/u/raj.speed1)
#### Post date: [November 19, 2020, 2:39pm UTC](https://discuss.elastic.co/t/elk-custom-time/256004/1 "2020-11-19T14:39:51Z")

</div>

Is there a way to disable relative time or last 1hr & enable user to select available or absolute date/time.

Im updating elk every 1hr with some constant parameters, using logstash.  
eg : now output\_value =101  
after 1hr, my output\_value can be 1231  
I dont want to average. So, Dashboard is designed to show current exact output\_value.  
Everytime I'm overriding the current report with the latest report values.  
Able to view the dashboard as per my requirement, when I select the time as **now**.

But, the problem here is, I dont have the details, for older entries.  
So, I stopped overriding  
& when I selected last 2hr or last 2days, Kibana is showing all the entries within the time gap & my dashboard is not showing the correct info.

Can anyone suggest/faced this kind of scenario..!!!

---

<div class="post-metadata">

### Author: ![wylie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wylie/32/81794_2.png) [@wylie](https://discuss.elastic.co/u/wylie)
#### Post date: [November 19, 2020, 6:28pm UTC](https://discuss.elastic.co/t/elk-custom-time/256004/2 "2020-11-19T18:28:33Z")

</div>

Since you only want to see the most recent update, ignoring all the previous values, how about you create a new index which only contains the latest update, deleting all the prior values? This way you will never see older data.

---

<div class="post-metadata">

### Author: ![raj.speed1](https://avatars.discourse-cdn.com/v4/letter/r/848f3c/32.png) [@raj.speed1](https://discuss.elastic.co/u/raj.speed1)
#### Post date: [November 20, 2020, 10:40am UTC](https://discuss.elastic.co/t/elk-custom-time/256004/3 "2020-11-20T10:40:09Z")

</div>

sounds good.. but every 1hr creating a new index may endup with number of indexes & dashboard.

---

<div class="post-metadata">

### Author: ![wylie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wylie/32/81794_2.png) [@wylie](https://discuss.elastic.co/u/wylie)
#### Post date: [November 20, 2020, 3:35pm UTC](https://discuss.elastic.co/t/elk-custom-time/256004/4 "2020-11-20T15:35:26Z")

</div>

You could automate the "most recent hour of data" using index aliases + Index Lifecycle Management. When the data is older than 1 hour you can move it to the rollover alias [https://www.elastic.co/guide/en/elasticsearch/reference/current/index-lifecycle-management.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-lifecycle-management.html)

---

<div class="post-metadata">

### Author: ![raj.speed1](https://avatars.discourse-cdn.com/v4/letter/r/848f3c/32.png) [@raj.speed1](https://discuss.elastic.co/u/raj.speed1)
#### Post date: [November 27, 2020, 9:39am UTC](https://discuss.elastic.co/t/elk-custom-time/256004/5 "2020-11-27T09:39:57Z")

</div>

Thanks Wylie.. Im trying your solution

---

<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 25, 2020, 9:40am UTC](https://discuss.elastic.co/t/elk-custom-time/256004/6 "2020-12-25T09:40:10Z")

</div>

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