# Indexing Date Ranges **URL:** \ **Category:** Elasticsearch\ **Created:** [December 7, 2015, 11:41am UTC](https://discuss.elastic.co/t/indexing-date-ranges/36524 "2015-12-07T11:41:13Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![colings86](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/colings86/32/44960_2.png) [@colings86](https://discuss.elastic.co/u/colings86)\ **Post date:** [December 7, 2015, 11:45am UTC](https://discuss.elastic.co/t/indexing-date-ranges/36524/2 "2015-12-07T11:45:22Z")
Maybe the following topic would be useful to you? It uses a start date and a duration but the approach could easily be modified to use a start and end date instead. > [@Display concurrency in data on Kibana](https://discuss.elastic.co/t/display-concurrency-in-data-on-kibana/26006/3): > > You can actually do this if you query Elasticsearch directly by using a script on a date\_histogram aggregation which adds the call document to all the buckets from the start\_time to start\_time + duration. The following gist contains a Sense recreation that details what I mean: [https://gist.github.com/jpountz/cebb8452648c36099cee](https://gist.github.com/jpountz/cebb8452648c36099cee) As for doing this in Kibana, I know it's possible to run scripts in Kibana for some actions but I'm not sure if this would be possible, maybe someone more familiar with… --- _[View the full topic](https://discuss.elastic.co/t/indexing-date-ranges/36524)._