You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 22, 2017. It is now read-only.
When I zoom in really far, the histogram stops showing any bars, even when data is present for the selected time range.
For example I have the following time range:
time must
field : @timestamp
from : "2013-11-15T19:29:35.552Z"
to : "2013-11-15T19:29:38.342Z"
The histogram does not show any bars, even though it reports values like "(18)" and "(16)" for the two searches and "(34 hits)" for the total entries. The table shows the textual representation of the 34 events.
This occurs in Chrome Version 28.0.1500.95 m and Firefox 17.0.8 on Windows.
The text was updated successfully, but these errors were encountered:
I'm also encountering the same issue with Kibana 3 milestone 4. Time intervals of less than 5 seconds being plotted on the graph will result in no bars displaying, e.g. 21:53:34 to 21:54:30. Lines and points get displayed when bars do not. I've tested with the current versions of Chrome, Firefox, Safari, and IE11.
Is this a bug or merely a limitation? I'd love if Kibana could simply switch from bars to lines for small time intervals.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When I zoom in really far, the histogram stops showing any bars, even when data is present for the selected time range.
For example I have the following time range:
time must
field : @timestamp
from : "2013-11-15T19:29:35.552Z"
to : "2013-11-15T19:29:38.342Z"
The histogram does not show any bars, even though it reports values like "(18)" and "(16)" for the two searches and "(34 hits)" for the total entries. The table shows the textual representation of the 34 events.
This occurs in Chrome Version 28.0.1500.95 m and Firefox 17.0.8 on Windows.
The text was updated successfully, but these errors were encountered: