# Parse UNIX timestamp as human readable date while moving the data into elasticsearch

**URL:** https://discuss.elastic.co/t/parse-unix-timestamp-as-human-readable-date-while-moving-the-data-into-elasticsearch/162317
**Category:** Logstash
**Created:** [December 28, 2018, 8:33am UTC](https://discuss.elastic.co/t/parse-unix-timestamp-as-human-readable-date-while-moving-the-data-into-elasticsearch/162317 "2018-12-28T08:33:57Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [December 29, 2018, 11:02am UTC](https://discuss.elastic.co/t/parse-unix-timestamp-as-human-readable-date-while-moving-the-data-into-elasticsearch/162317/2 "2018-12-29T11:02:53Z")

</div>

> [@amitnegi6190](#):
>
> "lastupdated" =\> "date"

You can only convert to types that exist in JSON (this only affects how the JSON documents being sent to Elasticsearch are formatted, not how Elasticsearch interprets and indexes these).

Your current date filter populates the @timestamp field. If you also want to store the other fields as dates I would probably do something like this (not tested):

```auto
date{
    match => ["lastUpdated", "UNIX_MS"]
    target => "lastUpdated"
}

date{
    match => ["firstUpdated", "UNIX_MS"]
    target => "firstUpdated"
}

```

---

_[View the full topic](https://discuss.elastic.co/t/parse-unix-timestamp-as-human-readable-date-while-moving-the-data-into-elasticsearch/162317)._