Hi Boaz,
So my epoch is not a date field:
"epoch" : {
"type" : "long"
},
I can probably test this fairly easy, but would that above work for
kibana if I store epoch as "epoch X 1000" ?
or would I need change the mapping to:
"epoch" : {
"type" : "date"
},
and insert "epoch x 1000" ?
Thanks for your resonse 
Edward
On 10/09/2013 12:30 PM, Boaz Leskes wrote:
Hi Edward,
Assuming your epoch time is in second, then yes, you need to multiply by
1000.
About kibana - if it is mapped as a date field it will work - regardless
of the input form - be it milliseconds epochs or an ISO formatted string.
Cheers,
Boaz
On Sunday, October 6, 2013 8:01:18 PM UTC+2, Edward Fjellskål wrote:
From:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html#date
<http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html#date>
"The date type will also accept a long number representing UTC
milliseconds since the epoch, regardless of the format it can handle."
Does that mean that I can save the epoch time + "000" and that
will be a valid date field?
Example:
Epoch: 1381041397
ES-Epoch: 1381041397000
Will that work also for the Kibana @timestamp field out of the box etc?
Regards,
Edward
--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.