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

Index pattern creation UX: Surface "no matching indices" error more clearly #10436

Closed
cjcenizal opened this issue Feb 17, 2017 · 1 comment
Closed
Labels
Team:Platform-Design Team Label for Kibana Design Team. Support the Analyze group of plugins.

Comments

@cjcenizal
Copy link
Contributor

Taken from #9991 (comment):

image

The message "Unable to fetch mapping. Do you have indices matching the pattern?" is too disconnected from the source of the error (the bad index pattern field). I think the solution is:

  • This button should just become disabled without changing text.
  • The index pattern field should be outlined in red.
  • There should be an error message below it that states, "Do you have indices matching this pattern? We couldn't fetch the mapping." (And what does "couldn't fetch the mapping mean"?" Doesn't it make more sense to say, "couldn't find any matching indices?")
@cjcenizal cjcenizal added Team:Platform-Design Team Label for Kibana Design Team. Support the Analyze group of plugins. :Management labels Feb 17, 2017
@cjcenizal cjcenizal changed the title Index creation UX: "Missing index" error reporting Index pattern creation UX: Surface missing indices error more clearly Feb 17, 2017
@cjcenizal cjcenizal changed the title Index pattern creation UX: Surface missing indices error more clearly Index pattern creation UX: Surface "no matching indices" error more clearly Feb 17, 2017
@cjcenizal
Copy link
Contributor Author

Addressed by #13454

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Platform-Design Team Label for Kibana Design Team. Support the Analyze group of plugins.
Projects
None yet
Development

No branches or pull requests

1 participant