Clarify error message. #469
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Elasticsearch will throw a 404 if there is no indexes added yet, resulting in this unclear message -- even for people that are not using any sort of proxy. This message update should make it easier to quickly troubleshoot why the the dialogue is popping up.
spalger
pushed a commit
that referenced
this pull request
Oct 6, 2014
Put the gridster 'preview' back
harper-carroll
pushed a commit
to harper-carroll/kibana
that referenced
this pull request
Jul 11, 2016
…cationOnly Classification Only Mode
This was referenced Mar 12, 2020
This was referenced Apr 27, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a clarification update that hopefully saves some time for new install troubleshooting.
Kibana makes a request to _all/_mapping in search of indexes, but will get back a 404 if the user has not added any elasticsearch indexes yet -- even though both elasticsearch and kibana are working perfectly fine.
This results in an ambiguous error message about a potential proxy issue.