# Keep Logstash from Crashing

**URL:** <https://discuss.elastic.co/t/keep-logstash-from-crashing/90392>\
**Category:** Logstash\
**Created:** [June 22, 2017, 5:45am UTC](https://discuss.elastic.co/t/keep-logstash-from-crashing/90392 "2017-06-22T05:45:37Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [June 22, 2017, 8:53am UTC](https://discuss.elastic.co/t/keep-logstash-from-crashing/90392/4 "2017-06-22T08:53:30Z")

</div>

The problem is that you're using the default `index` value for your elasticsearch output, "logstash-%{+YYYY.MM.dd}", which requires that the `@timestamp` field exists.

Can you temporarily replace your elasticsearch output with a `stdout { codec => rubydebug }` output so we can see exactly what the events look like? The error indicates that the event that causes the crash lacks a `@timestamp` field but the date filter should make sure that field exists.

---

_[View the full topic](https://discuss.elastic.co/t/keep-logstash-from-crashing/90392)._