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

[Ingest Node Pipelines] New description field for processors #56000

Closed
jloleysens opened this issue Apr 30, 2020 · 2 comments · Fixed by #57906
Closed

[Ingest Node Pipelines] New description field for processors #56000

jloleysens opened this issue Apr 30, 2020 · 2 comments · Fixed by #57906
Assignees
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP Team:Data Management Meta label for data/management team

Comments

@jloleysens
Copy link
Contributor

jloleysens commented Apr 30, 2020

Describe the feature:

Building UI for the managing processors in Kibana has shown how the tag field may be used to serve dual purposes:

  1. A unique identifier for a processor instance
  2. A descriptive name for the processor instance

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

@jloleysens jloleysens added the :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP label Apr 30, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features (:Core/Features/Ingest)

@jethr0null
Copy link

jethr0null commented May 20, 2020

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.

talevy added a commit to talevy/elasticsearch that referenced this issue Jun 9, 2020
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.
talevy added a commit that referenced this issue Jun 15, 2020
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.
talevy added a commit to talevy/elasticsearch that referenced this issue Jun 15, 2020
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.
talevy added a commit that referenced this issue Jun 16, 2020
…8152)

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP Team:Data Management Meta label for data/management team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants