-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
"Time mode requires the flot.time plugin" can throw even if flot.time.js is present - #195
Comments
It appears that this same issue occurs when attempting to parse through semi-large amounts of data to create a new graph. |
I've upgraded to flot 0.8.1 and haven't seen this issue |
spalger
pushed a commit
to spalger/kibana
that referenced
this issue
Mar 3, 2016
harper-carroll
pushed a commit
to harper-carroll/kibana
that referenced
this issue
Jul 11, 2016
w33ble
added a commit
to w33ble/kibana
that referenced
this issue
Sep 13, 2018
* chore: defaultValue -> default BREAKING CHANGE: the object definition changed, defaultValue will silently be dropped now * chore: description -> help BREAKING CHANGE: the object definition changed, description will silently be dropped now * fix: corrected spec for checkbox arg type * fix: update exactly and urlparm functoin specs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running newest version of Kibana, and this error threw after my elasticsearch cluster went down to a yellow-health from one of the cluster members changing its node names and not being able to find its partner.
The two are now playing nicely with each other and generating indexes, but I noticed that kibana was throwing this error for the timeline graph, even though the flot.time plugin exists, and is being used by three other kibana instances on the same server with no problem. The rest of kibana was updating with new events, so it appeared to be an issue just with the graph.
The error seems to be the same issue that was fixed here three months ago in flot: flot/flot#1016 is kibana using an older version of flot?
Issue fixed itself and the graph returned to a functioning state with no tinkering on my part after a few minutes, but it still seems relevant as a potential issue.
Update:
It still infrequently throws the same error; not sure what's causing it as it appears to be only this one instance of kibana which had the cluster failure.
The text was updated successfully, but these errors were encountered: