Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom range, right now, invalid range #867

Closed
Yann-- opened this issue Jan 24, 2014 · 1 comment · Fixed by #991
Closed

Custom range, right now, invalid range #867

Yann-- opened this issue Jan 24, 2014 · 1 comment · Fixed by #991
Labels
bug Fixes for quality problems that affect the customer experience

Comments

@Yann--
Copy link

Yann-- commented Jan 24, 2014

Hi,

I'm having fun with kibana 3 pre 5, but i have a strange behaviour. As i'm not sure it's a bug or a wrong configuration, i post it as a question.

SO here is my problem. let's say we are the 24th January.
If i specify from "2014/01/24 00:00:00" and let the To field set to "Right now", i have an "invali date or range" message.

In fact, the "right now" date is yesterday. so i have to specify 2014/01/24 23:00:00

The thing is if i want my dashboard refreshed every 15minutes from Midnight to right now, i can't.

Any idea ?

Yann

@soenkeliebau
Copy link

I have the same issue, "NOW" works well in queries and filters, but for the timepicker it is pretty much exactly 24h in the past from the current time.

This is probably related to the way that the timepicker code determines the current time which doesn't accomodate for timezones. If I set my system timezone to +13, the "right now" time in the timepicker moves forward as well..
Perhaps .getTimezoneOffset(); could be used to find the time difference between UTC time as returned by new Date(); and system time and then be adjusted for?

Is this potentially related to #903?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants
@soenkeliebau @rashidkpc @Yann-- and others