Adjust time according to local timezone

[bobrik]

If "browser" timezone is specified then date histograms for periods larger that 1h will be aligned to local timezone.

Here in Europe/Moscow (UTC+4) if you histogram interval is set to 1d then days start at 4AM. With this patch days are aligned to 00:00. It would be great if someone could confirm the same in their local timezone.

[bobrik]

Anyone?

[bobrik]

Looks like it only works well if you rotate indices at local midnight. Not sure if this is a good idea.

[rashidkpc]

We standardize on index rotation at UTC midnight.

[bobrik]

Yep, but this way it's impossible to get date histogram aligned to midnight at local timzone.

If you fire request with aligned timezone agains many indices at once, you'll get correct results, but if you do searching day by day — things get screwed up.

For example, this is index that is rotated on midnight UTC and request isn't using pre_timezone:

{
  "took" : 305,
  "timed_out" : false,
  "_shards" : {
    "total" : 5,
    "successful" : 5,
    "failed" : 0
  },
  "hits" : {
    "total" : 44314350,
    "max_score" : 1.0,
    "hits" : [ ]
  },
  "facets" : {
    "0" : {
      "_type" : "date_histogram",
      "entries" : [ {
        "time" : 1377648000000,
        "count" : 161002,
        "min" : 1.0,
        "max" : 121016.0,
        "total" : 5.4771627E7,
        "total_count" : 161002,
        "mean" : 340.19221500354035
      } ]
    }
  }
}

The next request is using timezone correction:

{
  "took" : 193,
  "timed_out" : false,
  "_shards" : {
    "total" : 5,
    "successful" : 5,
    "failed" : 0
  },
  "hits" : {
    "total" : 44314350,
    "max_score" : 1.0,
    "hits" : [ ]
  },
  "facets" : {
    "0" : {
      "_type" : "date_histogram",
      "entries" : [ {
        "time" : 1377633600000,
        "count" : 133903,
        "min" : 1.0,
        "max" : 121016.0,
        "total" : 4.8007871E7,
        "total_count" : 133903,
        "mean" : 358.52722493148025
      }, {
        "time" : 1377720000000,
        "count" : 27099,
        "min" : 1.0,
        "max" : 93157.0,
        "total" : 6763756.0,
        "total_count" : 27099,
        "mean" : 249.59430237278127
      } ]
    }
  }
}

Here we got 2 days.

The solution I see here: add up values in kibana itself so one point could actually come from two days. It will work for count and total, mean is tricky.

Maybe I should just give up and start everything with UTC. Not sure if everybody would be happy with such solution.

What do you think?

[willejs]

Everything in UTC!

[sagacity]

It would be very nice if the timepicker would also support picking dates in UTC (perhaps using a configuration setting).