Updated kbnIndex.indices function to issue for non-UTC users #1489
Conversation
…tc_tz. This option is a bool to determine if the user wishes to use UTC or local time when building a list of possible indexes based on the timestamp pattern on the index. This is extremely important for users who are implementing solutions that by their nature use local time and not UTC.
|
I have confirmed that this only works if the timestamp used on the Index is in the same timezone as the browser. I will work on a fix that allows you to define a timezone for the index timestamp and then convert any browser time to index timestamp when searching for indexes. |
|
Woops! Sorry about that! We recently replaced the master branch with Kibana 4. This action force closed all of the old pull requests against master. We will be reviewing these on a case-by-case basis and creating new tickets as necessary. The good news is that many long requested features can be found in Kibana 4, and we're being entirely open about our roadmap. Check out the roadmap tickets (which we're still filling in) here. If you're looking for the old Kibana 3 code you can find it here. |
|
Thanks for the submission, if you manage to resolve the issue, let us know. We've made some very significant upgrades to the code that chooses indices, so its possible that this is resolved in Kibana 4. |
|
I'll test with Kibana 4 and check to see if same issue manifests. Thanks! |
Updated kbnIndex.indices function to have a configuration option of utc_tz.
This option is a bool to determine if the user wishes to use UTC or local time when building a list of possible indexes based on the timestamp pattern on the index. This is extremely important for
users who are implementing solutions that by their nature use local time and not UTC.
Resolves #1487