-
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
[Discover] Improve shard error message formatting #161098
[Discover] Improve shard error message formatting #161098
Conversation
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍 thx for taking care of this. Tested locally and works as expected.
2 observations, potential follow ups
shard errors in Discover are still toasts ... they don't storm, but like error messages we should inline them. Same with embeddables on a dashboard ... there they could in theory create a storm, when you have a lot embeddables with different shard errors. Also on a dashboard it's not clear which toast belongs to which embeddables in such cases ... something we should aim to improve rather earlier than later, give that we should also aim to surface CCS to the user (like timeouts) ... but for sure nothing for this PR... here's the issue:
#155216
src/plugins/data/public/shard_failure_modal/shard_failure_description.tsx
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jughosta Great job! thanks for implementing so fast. LGTM. Just left a nit about the Show details
button.
src/plugins/data/public/shard_failure_modal/shard_failure_description.tsx
Outdated
Show resolved
Hide resolved
…ription.tsx Co-authored-by: Andrea Del Rio <[email protected]>
@sophiec20 can you please let us know what you think of this proposal? |
One small point of feedback - what size font is the page heading?... does it need to be so dominant?... it is the largest and boldest font on the entire page (including the base page) .. Otherwise LGTM and thank you .. |
Thanks, @sophiec20! Reduced the title size to 16px: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stratoula Good point! Updated: |
Awww much better Julia, thanx ❤️ |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Module Count
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: cc @jughosta |
- Closes elastic#156645 ## Summary This PR updates UI of shards error modal. ### Updated design <img width="500" alt="Screenshot 2023-07-07 at 10 05 00" src="https://github.com/elastic/kibana/assets/1415710/a099a436-61fd-4522-b231-88a0d1179061"> ![Jul-07-2023 10-20-13](https://github.com/elastic/kibana/assets/1415710/23069476-9aae-4c76-9e39-586a382dcf70) ### Before <img width="500" alt="image 2" src="https://github.com/elastic/kibana/assets/4016496/d3c067d9-2d18-4fcc-8db0-573defcb9b44"> For testing, please follow instruction from elastic#41649 and drop `targetfield` on Lens page. ### Checklist - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] This renders correctly on smaller devices using a responsive layout. (You can test this [in your browser](https://www.browserstack.com/guide/responsive-testing-on-local-server)) - [x] This was checked for [cross-browser compatibility](https://www.elastic.co/support/matrix#matrix_browsers) --------- Co-authored-by: Andrea Del Rio <[email protected]> Co-authored-by: Stratoula Kalafateli <[email protected]>
This is an aside, I've always thought that the 10 pop ups that appear simultaneously whenever I get a shard error is overwhelming and the need to close each pop up is similarly annoying. Is there any attempt to address this? Or has this been dealt with in the more recent versions? |
Hi @thekofimensah, I agree that seeing long lists of toast messages is really annoying. There's still work left to do, but we've been taking steps to address this issue in recent releases. These are some of the other improvements we've made already:
We're also currently working on overhauling how we handle and surface shard failures and cross cluster search errors, so users can expect more improvements in these areas soon. Hope this helps! |
Amazing, thanks for the response. I've been deploying the stack for 8 years
now so I'm seeing all the improvements and I've been enjoying seeing things
evolve! If you ever need feedback or anything from someone on the outside,
feel free to reach out :)
…On Wed, Sep 20, 2023, 4:26 PM Davis McPhee ***@***.***> wrote:
Hi @thekofimensah <https://github.com/thekofimensah>, I agree that seeing
long lists of toast messages is really annoying. There's still work left to
do, but we've been taking steps to address this issue in recent releases.
These are some of the other improvements we've made already:
- Both Discover and Lens now use inline warning displays for shard
errors instead of toasts, and this applies to their Dashboard panels as
well:
- #161271 <#161271>
- #147818 <#147818>
- We've reduced the number of separate shard failure warnings for the
same request by consolidating them under a single "incomplete data"
warning: #165512 <#165512>
- It's now possible to dismiss all toasts with a single action when
several appear at once: elastic/eui#7111
<elastic/eui#7111>
We're also currently working on overhauling how we handle and surface
shard failures and cross cluster search errors, so users can expect more
improvements in these areas soon. Hope this helps!
—
Reply to this email directly, view it on GitHub
<#161098 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFSNDF7PAO2266RX62XQ5LDX3N3QRANCNFSM6AAAAAAZ4PYKKQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Summary
This PR updates UI of shards error modal.
Updated design
Before
For testing, please follow instruction from #41649 and drop
targetfield
on Lens page.Checklist