Confusing error message when indexing is behind #471
Labels
Comments
|
I think the "selected time range" part is pretty clear. Also, I don't think index creation lag is the reason most people will see this error. Suppose it couldn't hurt to say something to the tune of "the latest one we found was for YYYY.MM.DD". |
|
Could you please help me how to solve this issue. |
stormpython
added a commit
that referenced
this issue
Oct 6, 2014
…tening for mouseover on chart titles which do not have an events object attached, so it could not have an eventResponse
|
When there are no records to show, Kibana 4 will say "No records found" but that's the best we can do. |
harper-carroll
pushed a commit
to harper-carroll/kibana
that referenced
this issue
Jul 11, 2016
Fixup name of AllConf proto file so it is picked up by generator
dgieselaar
added a commit
that referenced
this issue
Oct 4, 2019
This was referenced Mar 12, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When log indexing is getting a bit behind Kibana will display this error message:
No indices matched The pattern [logstash-]YYYY.MM.DD did not match any indices in your selected time range.This happens because Kibana can't find today's index when the default timespan is a few hours back. However, such indexes do exist for previous dates.
Maybe in the case Kibana found no "indices in your selected time range" it could go ahead and make additional check to see if there are at all such indices, and if there are it could say something about indexing being behind?
The text was updated successfully, but these errors were encountered: