Fails to find hourly indexes in time frames smaller than 3 hours

[Ralnoc]

I receive the error 'No results There were no results because no indices were found that match your selected time span' when using an hourly index and I try and find smaller increment time frames.

So if I was trying to find 5m, 15m, or 1h time frames after I have started using an hourly index it returns that error.

[Ralnoc]

Interestingly enough, if I just choose one of the smaller time frames from the pulldown it fails with the above error. However if I leave it at that time frame option (ie 5m) then click on the dashboard configuration and click save, then it displays the expected time frame information. Though it fails again if I click on update button in Kibana.

[Ralnoc]

This issue seems to revolve around the kbnIndex code. For some reason Kibana, with hourly indexes, can't seem to locate the indexes when you switch to smaller time increments.

The symptoms are that it will load fine if you edit the dashboard and then save, however every time you try and just load that time period it fails with a 'No results' error. In a template or script, if you set that time period as the default for the template it will fail and when you inspect a panel, the curl command has no indexes listed.

[Ralnoc]

Further investigation shows that if you set the default timespan to low enough to trigger this issue then try the open 'configure dashboard' then save to get it to reload, it doesn't load the data. Instead it appears to be retaining the index list from when you use the working larger timespan that works with the shorter timespan window.

Basically it seems that for some reason, when using the hour index timestamping, Kibana in unable to detect the indexes properly in shorter timespans.

[Ralnoc]

This appears to be a UTC conversion issue. Further investigation into the indices function under kbnIndex shows that when using a small timespan, it is returning UTC based hourly indexes that don't match the current timezone.

[Ralnoc]

This issue is resolved in #1489

[rashidkpc]

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.