# \[Solved\] Weekly indexes instead of daily

**URL:** <https://discuss.elastic.co/t/solved-weekly-indexes-instead-of-daily/56871>\
**Category:** Logstash\
**Created:** [August 1, 2016, 8:16am UTC](https://discuss.elastic.co/t/solved-weekly-indexes-instead-of-daily/56871 "2016-08-01T08:16:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![brayndasilva](https://avatars.discourse-cdn.com/v4/letter/b/2bfe46/32.png) [@brayndasilva](https://discuss.elastic.co/u/brayndasilva)\
**Post date:** [August 1, 2016, 8:16am UTC](https://discuss.elastic.co/t/solved-weekly-indexes-instead-of-daily/56871/1 "2016-08-01T08:16:15Z")

</div>

Right now I am working with indexes that are created daily using the following output in my config file:

```
output {
  elasticsearch {
    hosts => ["localhost:9200"]
    index => "logstash-events-%{+YYYY.MM.dd}"
  }
}

```

This is fine, but I was wondering if it is possible to have it make new indexes every week.

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [August 1, 2016, 3:12pm UTC](https://discuss.elastic.co/t/solved-weekly-indexes-instead-of-daily/56871/2 "2016-08-01T15:12:23Z")

</div>

Sure, use e.g. YYYY.ww as the timestamp format string. See [https://www.elastic.co/guide/en/logstash/current/event-dependent-configuration.html#sprintf](https://www.elastic.co/guide/en/logstash/current/event-dependent-configuration.html#sprintf) for details.

---

<div class="post-metadata">

**Author:** ![sandeepkanabar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sandeepkanabar/32/79399_2.png) [@sandeepkanabar](https://discuss.elastic.co/u/sandeepkanabar)\
**Post date:** [January 8, 2017, 1:43pm UTC](https://discuss.elastic.co/t/solved-weekly-indexes-instead-of-daily/56871/3 "2017-01-08T13:43:19Z")

</div>

A small note. Using `xxxx.ww` will be more preferable compared to `YYYY.ww`. `YYYY.ww` doesn't handle the rolling of year gracefully. So you could end up with 2017.52 in the first week of 2017. See [https://github.com/logstash-plugins/logstash-output-elasticsearch/issues/541#issuecomment-270923437](https://github.com/logstash-plugins/logstash-output-elasticsearch/issues/541#issuecomment-270923437)

---

<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:** [July 6, 2017, 4:29am UTC](https://discuss.elastic.co/t/solved-weekly-indexes-instead-of-daily/56871/4 "2017-07-06T04:29:31Z")

</div>