-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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 Node Pipelines] New description field for processors #56000
Comments
Pinging @elastic/es-core-features (:Core/Features/Ingest) |
To add a bit of context around how we'd like to use this field, I'll provide an example in the context of the Ingest Nodes Pipeline UI that the team is currently working on. When displaying a list of processors within a pipeline visually, it's more difficult to determine which processor is responsible for which changes without the presence of a processor description. Here is an example mockup that highlights where these descriptions would be used in order to make it easier for users to quickly see information about the processor beyond the processor name and identify the specific processor they intend to edit/delete/etc. |
This commit adds an optional field, `description`, to all ingest processors so that users can explain the purpose of the specific processor instance. Closes elastic#56000.
This commit adds an optional field, `description`, to all ingest processors so that users can explain the purpose of the specific processor instance. Closes #56000.
This commit adds an optional field, `description`, to all ingest processors so that users can explain the purpose of the specific processor instance. Closes elastic#56000.
Describe the feature:
Building UI for the managing processors in Kibana has shown how the
tag
field may be used to serve dual purposes:It would be really useful to have an extra (optional)
description
field when creating a processor so that the tag can be more singular in its concern.CC @jakelandis @talevy
The text was updated successfully, but these errors were encountered: