Kibana is converting times into UTC before sending them to ES.
Here is the custom date range:
ES query shows: "range": { "TakeoffTime": { "from": 1441541033725, "to": 1441660635743 } }
1441541033725 -> 2015-09-06 12:03:54
1441660635743 -> 2015-09-07 21:17:16
So what we can do to force Kibana use UTC across all panels? we don't want to deal with browser/local time at all.
Kibana is converting times into UTC before sending them to ES.
It's Logstash that sends data to ES. But yes, Logstash's date filter normalizes all timestamps to UTC.
So what we can do to force Kibana use UTC across all panels? we don't want to deal with browser/local time at all.
This was discussed a few days ago:
Continuing the discussion from Kibana Timezone :
Is there any options for Kibana not to convert @timestamp from UTC to browser local timezone?
We are not using Logstash. When Kibana sends a request like below, it converts selected date into UTC. We are already storing dates in UTC in ES and we want to use all dates in Kibana as UTC.
curl -XGET 'http://pse-dev-noc02.mascorp.com:9201/flight_outages- /_search?pretty' -d '{
"facets": {
"terms": {
"terms": {
"field": "operator",
"size": 10,
"order": "count",
"exclude": []
},
"facet_filter": {
"fquery": {
"query": {
"filtered": {
"query": {
"bool": {
"should": [
{
"query_string": {
"query": " "
}
}
]
}
},
"filter": {
"bool": {
"must": [
{
"range": {
"TakeoffTime": {
"from": 1441541033725,
"to": 1441660635743
}
}
}
]
}
}
}
}
}
}
}
},
"size": 0
}'
We are not using Logstash. When Kibana sends a request like below, it converts selected date into UTC.
Right, I didn't get that you were talking about the requests and not the data itself. Anyway, the issue reference I gave still applies.