-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Ingest Pipelines] Error messages #70167
[Ingest Pipelines] Error messages #70167
Conversation
@elasticmachine merge upstream |
Pinging @elastic/es-ui (Team:Elasticsearch UI) |
@jloleysens Could you add a screenshot of how the error looks with these changes? |
@elasticmachine merge upstream |
@cjcenizal Made some minor adjustments to copy and layout and updated the PR description with screenshots. |
This is much better! Does the 'Show 3 errors' need to read 'Show 3 more errors'? or '+ 3 more'? Can we limit the number shown by default (before hiding them) down to 4 or 5 or so? |
@mdefazio I took the copy from the collapsible list we have in snapshot & restore which does not have the "more" and "less" in it. We can ask someone from docs to also weigh in. Currently the number of errors is limited to 5, we can go down to 4 if you think that would look better? |
Ah sorry, I mixed up the screenshots trying to go too fast. 5 is good. :D My initial reaction was that it wasn't clear enough that hitting the link would show 3 additional errors. If there are 5 shown, and 5 hidden, maybe this would be confusing. I think it's good we stay consistent, but might be worth having someone from docs weigh in. |
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.
This makes the errors much easier to parse. Nice work @jloleysens!
I agree with @mdefazio regarding the "more/less" copy - I think it's worth reaching out to the docs team to see their thoughts. I also wonder if it would be more readable if the list items were formatted something like: "bytes processor: [field] required property is missing". WDYT?
Also, is it possible to add some tests for this change?
...plugins/ingest_pipelines/public/application/components/pipeline_form/pipeline_form_error.tsx
Outdated
Show resolved
Hide resolved
...plugins/ingest_pipelines/public/application/components/pipeline_form/pipeline_form_error.tsx
Outdated
Show resolved
Hide resolved
@elasticmachine merge upstream |
@elasticmachine merge upstream |
Also added missing translation and refactored maximum errors in collapsed state to external constant
@alisonelizabeth @mdefazio thanks both for the feedback. I believe I have addressed the feedback points provided. Would you please take another look? |
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.
Latest changes LGTM. Thanks for adding tests!
💚 Build SucceededBuild metrics@kbn/optimizer bundle module count
History
To update your PR or re-run it, just comment with: |
* improved error messages * traverse recursive error struct * add check for object with keys * update button position and copy * size adjustments * Refactor i18n texts and change wording Also added missing translation and refactored maximum errors in collapsed state to external constant * use io-ts, add CIT and unit tests * refactor error utilities to separate file Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* master: (46 commits) [Visualize] Add missing advanced settings and custom label for pipeline aggs (elastic#69688) Use dynamic: false for config saved object mappings (elastic#70436) [Ingest Pipelines] Error messages (elastic#70167) [APM] Show transaction rate per minute on Observability Overview page (elastic#70336) Filter out error when calculating a label (elastic#69934) [Visualizations] Each visType returns its supported triggers (elastic#70177) [Telemetry] Report data shippers (elastic#64935) Reduce SavedObjects mappings for Application Usage (elastic#70475) [Lens] fix dimension label performance issues (elastic#69978) Skip failing endgame tests (elastic#70548) [SIEM] Reenabling Cypress tests (elastic#70397) [SIEM][Security Solution][Endpoint] Endpoint Artifact Manifest Management + Artifact Download and Distribution (elastic#67707) [Security] Adds field mapping support to rule creation (elastic#70288) SECURITY-ENDPOINT: add fields for events to metadata document (elastic#70491) Fixed assertion in hybrid index pattern test to iterate through indices (elastic#70130) [SIEM][Exceptions] - Exception builder component (elastic#67013) [Ingest Manager] Rename data sources to package configs (elastic#70259) skip suites blocking es snapshot promomotion (elastic#70532) [Metrics UI] Fix asynchronicity and error handling in Snapshot API (elastic#70503) fix export response (elastic#70473) ...
* improved error messages * traverse recursive error struct * add check for object with keys * update button position and copy * size adjustments * Refactor i18n texts and change wording Also added missing translation and refactored maximum errors in collapsed state to external constant * use io-ts, add CIT and unit tests * refactor error utilities to separate file Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Summary
Compresses error feedback when attempting to create or update a pipeline.
Currently pipeline errors are reported as one continuous string (see screenshot). This PR adds code for parsing and displaying errors in a more user friendly way.
How to test
{}
for config (so you know it is invalid).Additional notes
Replicates the pattern in Snapshot & Restore of collapsible indices list
Screenshots
Current errors
After changes