[DOCS] Update ingest node pipeline refs (#78770)

In https://github.com/elastic/kibana/pull/113783, we renamed Kibana's **Ingest Pipelines** feature to **Ingest Pipelines**. This updates screenshots and references for the feature. It also replaces a few remaining `ingest node pipeline` references.
This commit is contained in:
James Rodewig 2021-10-12 08:18:24 -04:00 committed by GitHub
parent df32157a99
commit a763a86a0d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
6 changed files with 14 additions and 14 deletions

Binary file not shown.

Before

Width:  |  Height:  |  Size: 44 KiB

After

Width:  |  Height:  |  Size: 42 KiB

Before After
Before After

View file

@ -313,14 +313,14 @@ Defaults to `*`, which matches all fields eligible for
[[index-default-pipeline]]
`index.default_pipeline`::
The default <<ingest,ingest node>> pipeline for this index. Index requests will fail
Default <<ingest,ingest pipeline>> for the index. Index requests will fail
if the default pipeline is set and the pipeline does not exist. The default may be
overridden using the `pipeline` parameter. The special pipeline name `_none` indicates
no ingest pipeline should be run.
[[index-final-pipeline]]
`index.final_pipeline`::
The final <<ingest,ingest node>> pipeline for this index. Indexing requests
`index.final_pipeline`::
Final <<ingest,ingest pipeline>> for the index. Indexing requests
will fail if the final pipeline is set and the pipeline does not exist.
The final pipeline always runs after the request pipeline (if specified) and
the default pipeline (if it exists). The special pipeline name `_none`

View file

@ -12,9 +12,9 @@ transformed documents to your data stream or index.
image::images/ingest/ingest-process.svg[Ingest pipeline diagram,align="center"]
You can create and manage ingest pipelines using {kib}'s **Ingest Node
Pipelines** feature or the <<ingest-apis,ingest APIs>>. {es} stores pipelines in
the <<cluster-state,cluster state>>.
You can create and manage ingest pipelines using {kib}'s **Ingest Pipelines**
feature or the <<ingest-apis,ingest APIs>>. {es} stores pipelines in the
<<cluster-state,cluster state>>.
[discrete]
[[ingest-prerequisites]]
@ -27,7 +27,7 @@ with the `ingest` role. For heavy ingest loads, we recommend creating
* If the {es} security features are enabled, you must have the `manage_pipeline`
<<privileges-list-cluster,cluster privilege>> to manage ingest pipelines. To use
{kib}'s **Ingest Node Pipelines** feature, you also need the
{kib}'s **Ingest Pipelines** feature, you also need the
`cluster:monitor/nodes/info` cluster privileges.
* Pipelines including the `enrich` processor require additional setup. See
@ -37,7 +37,7 @@ with the `ingest` role. For heavy ingest loads, we recommend creating
[[create-manage-ingest-pipelines]]
=== Create and manage pipelines
In {kib}, open the main menu and click **Stack Management** > **Ingest Node
In {kib}, open the main menu and click **Stack Management** > **Ingest
Pipelines**. From the list view, you can:
* View a list of your pipelines and drill down into details
@ -48,7 +48,7 @@ To create a new pipeline, click **Create pipeline**. For an example tutorial,
see <<common-log-format-example>>.
[role="screenshot"]
image::images/ingest/ingest-pipeline-list.png[Kibana's Ingest Node Pipelines list view,align="center"]
image::images/ingest/ingest-pipeline-list.png[Kibana's Ingest Pipelines list view,align="center"]
You can also use the <<ingest-apis,ingest APIs>> to create and manage pipelines.
The following <<put-pipeline-api,create pipeline API>> request creates

View file

@ -23,11 +23,11 @@ These logs contain a timestamp, IP address, and user agent. You want to give
these three items their own field in {es} for faster searches and
visualizations. You also want to know where the request is coming from.
. In {kib}, open the main menu and click **Stack Management** > **Ingest Node
. In {kib}, open the main menu and click **Stack Management** > **Ingest
Pipelines**.
+
[role="screenshot"]
image::images/ingest/ingest-pipeline-list.png[Kibana's Ingest Node Pipelines list view,align="center"]
image::images/ingest/ingest-pipeline-list.png[Kibana's Ingest Pipelines list view,align="center"]
. Click **Create pipeline**.
. Provide a name and description for the pipeline.
@ -74,7 +74,7 @@ the processors as follows:
Your form should look similar to this:
[role="screenshot"]
image::images/ingest/ingest-pipeline-processor.png[Processors for Ingest Node Pipelines,align="center"]
image::images/ingest/ingest-pipeline-processor.png[Processors for Ingest Pipelines,align="center"]
The four processors will run sequentially: +
Grok > Date > GeoIP > User agent +

View file

@ -65,7 +65,7 @@ Grants full access to all features in {kib} (including Solutions) and read-only
[[built-in-roles-enrich-user]] `enrich_user` ::
Grants access to manage *all* enrich indices (`.enrich-*`) and *all* operations on
ingest node pipelines.
ingest pipelines.
[[built-in-roles-ingest-user]] `ingest_admin` ::
Grants access to manage *all* index templates and *all* ingest pipeline configurations.

View file

@ -61,7 +61,7 @@ All {Ilm} operations related to managing policies.
All operations on index templates.
`manage_ingest_pipelines`::
All operations on ingest node pipelines.
All operations on ingest pipelines.
`manage_logstash_pipelines`::
All operations on logstash pipelines.