-
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] Processor forms for processors A-D #72849
[Ingest Pipelines] Processor forms for processors A-D #72849
Conversation
- Also refactored options to live in scoped objects to avoid overriding type (important fix!) - Have not polished copy or form layout.
- date_index_name - dissect - dot_expander - drop Fields refactored: - Field - Ignore missing
Pinging @elastic/es-ui (Team:Elasticsearch UI) |
@elasticmachine merge upstream |
...mponents/pipeline_processors_editor/components/processor_settings_form/processors/circle.tsx
Outdated
Show resolved
Hide resolved
...ponents/pipeline_processors_editor/components/processor_settings_form/processors/convert.tsx
Outdated
Show resolved
Hide resolved
@elasticmachine merge upstream |
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 is looking great @jloleysens! I did a light code review and verified all the processor types against the docs. I have not yet thoroughly tested adding the processor types and then creating/saving the pipeline. I also think it'd be great to get some of the ES engineers to review these forms for a sanity check.
Bugs
- There were a few processor types where the
field
field wasn't marked as required:csv
,date_index_name
, anddissect
. - ? If I select the
append
processor type (for example), fill out the required fields and update, then go back to edit it and change processor types, any fields that were common retained the value. I think I would expect the fields to be cleared in this scenario.
UX feedback
- It'd be great if we could make the "Condition" field more usable, similarly with "Pattern" (possibly others). I think both of these could potentially be fairly long, which could make the text field hard to work with.
- I'm not used to seeing radio groups 😄 . This may be a personal preference, but what do you think about using a dropdown for the shape types instead (
circle
processor)? - I think we could borrow some of the UX in the mappings editor, where we use the toggle for optional fields. Also, I think it's really helpful to have help text next to each field as well. The doc link may not be applicable.
- I noticed some of the optional fields have "(optional)" in the field name, and some do not. This point may not be applicable though if we follow the mappings editor UX.
- How difficult would it be to use a human-readable name for the processor type in the dropdown? For example, "date index name" instead of "date_index_name".
Other
- I noticed the ability to add an
on_failure
processor at the processor level is missing. Are you planning to add support for this?
<UseField | ||
componentProps={{ | ||
euiFieldProps: { | ||
options: [ |
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.
Per the docs, long
is also supported here. https://www.elastic.co/guide/en/elasticsearch/reference/master/convert-processor.html
@elasticmachine merge upstream |
@elasticmachine merge upstream |
…nes/processor-forms-a-d * 'master' of github.com:elastic/kibana: (26 commits) [Telemetry][API Integration] size_in_bytes to be a number (elastic#74664) [ILM] Convert node details flyout to TS (elastic#73707) [Ingest Node Pipelines] Sentence-case processor names (elastic#74645) Bump angular dependency from 1.7.9 to 1.8.0 (elastic#74482) [ML] Fixing schema for custom rule conditions (elastic#74676) [ML] Refactor in preparation for new es client (elastic#74552) [ML] Adding initial file analysis overrides (elastic#74376) Allow any hostname for chromium proxy bypass (elastic#74693) [ML] ML on Kibana Management: Add ability to pass a group ID filter to job management page (elastic#74533) [Metrics UI] Fix No Data preview pluralization (elastic#74399) [Bug][Security_Solution][Telemetry] Capitalize S in macOS (elastic#74688) Remove karma tests from legacy maps (elastic#74668) [Ingest Manager] stop creating events-* index pattern and placeholder index (elastic#74683) [Enterprise Search] Update the browser/document title on plugin navigation (elastic#74392) [visualizations] Add i18n translation for 'No results found' (elastic#74619) [maps] convert vector style properties to TS (elastic#74553) bump geckodriver binary to 0.27 (elastic#74638) fix: update apm agents to catch abort requests (elastic#74658) [Security Solution] Resolver children pagination (elastic#74603) add memoryStatus to df analytics page and analytics table in management (elastic#74570) ...
- Added help text for all fields - Updated layout so that required fields are always on first - Replaced circle radio group with a select drop down
👍 I will open up a separate issue to address this.
I'll defer to Michael, but I think that makes sense and would be interested in seeing how that would 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. Nice job!
I had two suggestions, but not blocking:
- The
append
processor accepts an array for thevalue
field. It might make more sense to use the combo box here instead of a text input. - It might be nice to add some client validation for the
dot_expander
processor, to ensure thefield
contains at least one.
character.
Another thought - I don't want to speak for the docs team, but I wonder if it would be easier for them to review the copy as part of this PR, rather than all of the forms at once.
Would it be possible to get review on new copy added in this PR? Most of the new copy added is in |
@alisonelizabeth Excellent points I'll address both of them (append and dot expander) and reach out to es-docs for review. |
@elasticmachine merge upstream |
💚 Build SucceededBuild metrics@kbn/optimizer bundle module count
async chunks size
page load bundle size
History
To update your PR or re-run it, just comment with: |
* First few processors of the first batch - Also refactored options to live in scoped objects to avoid overriding type (important fix!) - Have not polished copy or form layout. * add type to shared imports * Refactors for repeated fields and added forms - date_index_name - dissect - dot_expander - drop Fields refactored: - Field - Ignore missing * Fix broken imports and some other small refactors * added text editor field and updated pattern and if fields * Large copy improvements and updates and other small refactors - Added help text for all fields - Updated layout so that required fields are always on first - Replaced circle radio group with a select drop down * update circle shape type field to select * Added "long" option for convert type * fix path import * fix types and i18n * add validation for dot expander fix append value to be a combobox * fix i18n Co-authored-by: Elastic Machine <[email protected]>
I created #74950 to track this enhancement @jloleysens @alisonelizabeth |
* upstream/master: (45 commits) [Metrics UI] Fix inventory footer misalignment (elastic#74707) Remove legacy optimizer (elastic#73154) Update design-specific GH code-owners (elastic#74877) skip test Reporting paginates content elastic#74922 [Metrics UI] Add Jest tests for alert previews (elastic#74890) Fixed tooltip (elastic#74074) [Ingest Pipelines] Processor forms for processors A-D (elastic#72849) [Observability] change ingest manager link (elastic#74928) [Task manager] Prevents edge case where already running tasks are reschedule every polling interval (elastic#74606) [Security Solution] Fix the status of timelines' bulk actions (elastic#74560) Data plugin: Suggested enhance pattern (elastic#74505) Use jest.useFakeTimers instead of hard coded timeout for tooltip tests. (elastic#74642) [Security Solution][lists] Adds tests for exception lists and items part 2 (elastic#74815) [Security Solution][Resolver] fix presentation role on edgeline (elastic#74869) [Security Solution][Detections] Refactor ML calls for newest ML permissions (elastic#74582) [bin/kibana-plugin] support KP plugins instead (elastic#74604) Reduce number of indexed fields in index pattern saved object (elastic#74817) [reporting] Pass along generic parameters in high-order route handler (elastic#74892) Migrated last pieces of legacy fixture code (elastic#74470) Empty index patterns page re-design (elastic#68819) ...
* First few processors of the first batch - Also refactored options to live in scoped objects to avoid overriding type (important fix!) - Have not polished copy or form layout. * add type to shared imports * Refactors for repeated fields and added forms - date_index_name - dissect - dot_expander - drop Fields refactored: - Field - Ignore missing * Fix broken imports and some other small refactors * added text editor field and updated pattern and if fields * Large copy improvements and updates and other small refactors - Added help text for all fields - Updated layout so that required fields are always on first - Replaced circle radio group with a select drop down * update circle shape type field to select * Added "long" option for convert type * fix path import * fix types and i18n * add validation for dot expander fix append value to be a combobox * fix i18n Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
Hey @jloleysens -- @lockewritesdocs agreed to look at the UI copy for this one. I'll handle #75054. Thanks for bringing this to our attention! |
Summary
Added forms for the following processors:
How to test
Notes
Checklist
For maintainers