# Need help with custom date format "timestamp": "2016-01-28T17:48:00.2286427Z"
**URL:** https://discuss.elastic.co/t/need-help-with-custom-date-format-timestamp-2016-01-28t17-48-00-2286427z/40401
**Category:** Elasticsearch
**Created:** [January 28, 2016, 5:59pm UTC](https://discuss.elastic.co/t/need-help-with-custom-date-format-timestamp-2016-01-28t17-48-00-2286427z/40401 "2016-01-28T17:59:44Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@anhlqn](https://discuss.elastic.co/u/anhlqn)
#### Post date: [January 28, 2016, 5:59pm UTC](https://discuss.elastic.co/t/need-help-with-custom-date-format-timestamp-2016-01-28t17-48-00-2286427z/40401/1 "2016-01-28T17:59:44Z")
Hi everyone,
I have an application that sends in logs with date format: `2016-01-28T17:48:00.2286427Z` (timestamp field)
It looks like that no built in format would support parsing this, so I give custom date format a try. I have tried a few of them but none succeeded. Below are a few format I tried:
> yyyyMMdd'T'HHmmss.SSSSSSSZ
> yyyy-MM-dd'T'HH:mm:ss.SSSSSSSZ
> yyyyMMdd HHmmss.SSSSSSSZ
> yyyy-MM-dd HH:mm:ss.SSSSSSSZ
The error message is
> MapperParsingException[failed to parse [timestamp]]; nested: IllegalArgumentException[Invalid format: "2016-01-28T17:47:52.4335142Z" is malformed at ":47:52.4335142Z"];
It's not my application and I have no idea where they get the 7 digit millisecond part from. Is there any valid format that can parse this timestamp or should I need to work with the log source to change to output format?
Thanks,
Anh
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 11:20pm UTC](https://discuss.elastic.co/t/need-help-with-custom-date-format-timestamp-2016-01-28t17-48-00-2286427z/40401/2 "2017-07-05T23:20:41Z")