diff --git a/docs/reference/images/ingest/ingest-pipeline-list.png b/docs/reference/images/ingest/ingest-pipeline-list.png index 1d3281e66922..12887fcbb3f2 100644 Binary files a/docs/reference/images/ingest/ingest-pipeline-list.png and b/docs/reference/images/ingest/ingest-pipeline-list.png differ diff --git a/docs/reference/index-modules.asciidoc b/docs/reference/index-modules.asciidoc index 5c721311afeb..d0e30cc97508 100644 --- a/docs/reference/index-modules.asciidoc +++ b/docs/reference/index-modules.asciidoc @@ -313,14 +313,14 @@ Defaults to `*`, which matches all fields eligible for [[index-default-pipeline]] `index.default_pipeline`:: - The default <> pipeline for this index. Index requests will fail + Default <> 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 <> pipeline for this index. Indexing requests +`index.final_pipeline`:: +Final <> 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` diff --git a/docs/reference/ingest.asciidoc b/docs/reference/ingest.asciidoc index 81cee132905c..b0d6859a051f 100644 --- a/docs/reference/ingest.asciidoc +++ b/docs/reference/ingest.asciidoc @@ -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 <>. {es} stores pipelines in -the <>. +You can create and manage ingest pipelines using {kib}'s **Ingest Pipelines** +feature or the <>. {es} stores pipelines in the +<>. [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` <> 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 <>. [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 <> to create and manage pipelines. The following <> request creates diff --git a/docs/reference/ingest/common-log-format-example.asciidoc b/docs/reference/ingest/common-log-format-example.asciidoc index 05f012ab5344..ce6b4a5e734d 100644 --- a/docs/reference/ingest/common-log-format-example.asciidoc +++ b/docs/reference/ingest/common-log-format-example.asciidoc @@ -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 + diff --git a/x-pack/docs/en/security/authorization/built-in-roles.asciidoc b/x-pack/docs/en/security/authorization/built-in-roles.asciidoc index d9db89b7880b..7a63d502b2a7 100644 --- a/x-pack/docs/en/security/authorization/built-in-roles.asciidoc +++ b/x-pack/docs/en/security/authorization/built-in-roles.asciidoc @@ -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. diff --git a/x-pack/docs/en/security/authorization/privileges.asciidoc b/x-pack/docs/en/security/authorization/privileges.asciidoc index 433afde6039b..64ffab8f5cb1 100644 --- a/x-pack/docs/en/security/authorization/privileges.asciidoc +++ b/x-pack/docs/en/security/authorization/privileges.asciidoc @@ -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.