# Issue parsing date
**URL:** https://discuss.elastic.co/t/issue-parsing-date/89569
**Category:** Logstash
**Created:** [June 15, 2017, 2:05pm UTC](https://discuss.elastic.co/t/issue-parsing-date/89569 "2017-06-15T14:05:24Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Peter\_Dwyer](https://discuss.elastic.co/u/Peter_Dwyer)
#### Post date: [June 15, 2017, 2:05pm UTC](https://discuss.elastic.co/t/issue-parsing-date/89569/1 "2017-06-15T14:05:24Z")
i'm having trouble figuring out what is wrong with my date filter.
```
"error"=>{"type"=>"mapper_parsing_exception", "reason"=>"failed to parse [datetime]", "caused_by"=>{"type"=>"illegal_argument_exception", "reason"=>"Invalid format: \"2017-06-15 14:57:36\" is malformed at \" 14:57:36\""}}}
```
The match im using is
```
match => ["datetime", "yyyy-MM-dd HH:mm:ss"]
```
i can see it seems to have an issue with the start of the time part but i dont understand why.
---
### Author:  [@Peter\_Dwyer](https://discuss.elastic.co/u/Peter_Dwyer)
#### Post date: [June 15, 2017, 2:27pm UTC](https://discuss.elastic.co/t/issue-parsing-date/89569/2 "2017-06-15T14:27:08Z")
it seems that this was being parsed elsewhere in the config. once i renamed it it started working correctly.
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [June 15, 2017, 7:40pm UTC](https://discuss.elastic.co/t/issue-parsing-date/89569/3 "2017-06-15T19:40:20Z")
It's Elasticsearch complaining, not Logstash. When this happens you need to inspect the field's mapping in ES.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 13, 2017, 7:40pm UTC](https://discuss.elastic.co/t/issue-parsing-date/89569/4 "2017-07-13T19:40:26Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.