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

Add a "Details" Link to the warning notification #3909

Closed
derjohn opened this issue May 21, 2015 · 1 comment
Closed

Add a "Details" Link to the warning notification #3909

derjohn opened this issue May 21, 2015 · 1 comment

Comments

@derjohn
Copy link

derjohn commented May 21, 2015

Hello Kibana Devs,
I had some painful fun in finding the cause for "Courier Fetch: X of Y shards failed". I am aware that kibana only hands over what's in the response from ES. At the end I had to use the webdeveloper toolbar to see that the (ajax) request to elasticsearch

"..../elasticsearch/_msearchtimeout=0&ignore_unavailable=true&preference=..."

contains useful information about the cause for the shards fetch failure:

{"responses":[{"took":237,"timed_out":false,"_shards":{"total":345,"successful":330,"failed":15,"failures":
....... nested: SearchParseException[[indexname-2015.05.21][10]: from[-1],size[-1]: Parse Failure [Failed to parse source .....  nested: ElasticsearchParseException[failed to parse date field [somedata], tried both date format [dateOptionalTime], and timestamp number]; nested: IllegalArgumentException[Invalid format: ....

I propose to have a "Details" Button on the Yellow Warning bar on top of the page that contains a popup with the errormessage in full text. Mabe the behavior could be configurable for those who don't to confuse their users.

rgds,
derjohn

@rashidkpc rashidkpc changed the title Courier Fetch: Add a "Details" Link to the Yellow Warning bar. Add a "Details" Link to the warning notification May 21, 2015
@timroes
Copy link
Contributor

timroes commented Mar 30, 2018

Our notification system has been replaced by EUI's new toast notifications, and thus I will close this in favor of the new EUI issue: elastic/eui#393

@timroes timroes closed this as completed Mar 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants