# "\_dateparsefailure" Logstash 6.2.1

**URL:** <https://discuss.elastic.co/t/dateparsefailure-logstash-6-2-1/125196>\
**Category:** Logstash\
**Created:** [March 22, 2018, 1:30pm UTC](https://discuss.elastic.co/t/dateparsefailure-logstash-6-2-1/125196 "2018-03-22T13:30:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mruthyu](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@mruthyu](https://discuss.elastic.co/u/mruthyu)\
**Post date:** [March 22, 2018, 1:30pm UTC](https://discuss.elastic.co/t/dateparsefailure-logstash-6-2-1/125196/1 "2018-03-22T13:30:16Z")

</div>

Even though the datetime field is parsed properly by logstash pipeline, every document in elasticsearch has  
"tags": [  
"\_dateparsefailure"  
],

So wondering why the tags field is getting populated with \_dateparsefailure

---

<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:** [March 22, 2018, 1:40pm UTC](https://discuss.elastic.co/t/dateparsefailure-logstash-6-2-1/125196/2 "2018-03-22T13:40:51Z")

</div>

Perhaps you have an extra file with an invalid date filter in /etc/logstash/conf.d (or wherever you keep your config files)? If you increase the loglevel Logstash will tell you exactly what configuration it loads. Make sure it's what you expect.

---

<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:** [April 19, 2018, 1:40pm UTC](https://discuss.elastic.co/t/dateparsefailure-logstash-6-2-1/125196/3 "2018-04-19T13:40:56Z")

</div>

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