[DOCS] Update ES ingest pipeline refs (#28239)

## What does this PR do? Changes several 'ingest node' references in the docs to 'ingest pipeline.' ## Why is it important? While a node with the `ingest` role is required to use Elasticsearch ingest pipelines, we no longer include 'ingest node' in the feature name. There are no official plans, but the Elasticsearch team has discussed removing the `ingest` role in the future. ## Related issues - elastic/elasticsearch#70253 - elastic/elasticsearch#78633 Co-authored-by: dedemorton <[email protected]>
elastic · Oct 5, 2021 · c3cb365 · c3cb365
1 parent e0cc99f
commit c3cb365
Show file tree

Hide file tree

Showing 38 changed files with 75 additions and 75 deletions.
diff --git a/auditbeat/auditbeat.reference.yml b/auditbeat/auditbeat.reference.yml
@@ -479,7 +479,7 @@ output.elasticsearch:
   # In case you modify this pattern you must update setup.template.name and setup.template.pattern accordingly.
   #index: "auditbeat-%{[agent.version]}-%{+yyyy.MM.dd}"
 
-  # Optional ingest node pipeline. By default no pipeline will be used.
+  # Optional ingest pipeline. By default no pipeline will be used.
   #pipeline: ""
 
   # Optional HTTP path

diff --git a/auditbeat/docs/fields.asciidoc b/auditbeat/docs/fields.asciidoc
@@ -2358,7 +2358,7 @@ alias to: error.message
 [float]
 === geoip
 
-The geoip fields are defined as a convenience in case you decide to enrich the data using a geoip filter in Logstash or Ingest Node.
+The geoip fields are defined as a convenience in case you decide to enrich the data using a geoip filter in Logstash or an Elasticsearch geoip ingest processor.
 
 
 

diff --git a/auditbeat/module/auditd/_meta/fields.yml b/auditbeat/module/auditd/_meta/fields.yml
@@ -858,7 +858,8 @@
     type: group
     description: >
       The geoip fields are defined as a convenience in case you decide to
-      enrich the data using a geoip filter in Logstash or Ingest Node.
+      enrich the data using a geoip filter in Logstash or an Elasticsearch geoip
+      ingest processor.
     fields:
       - name: continent_name
         type: keyword

diff --git a/auditbeat/module/auditd/fields.go b/auditbeat/module/auditd/fields.go
diff --git a/docs/devguide/modules-dev-guide.asciidoc b/docs/devguide/modules-dev-guide.asciidoc
@@ -304,10 +304,9 @@ variables to dynamically switch between configurations.
 [float]
 ==== ingest/*.json
 
-The `ingest/` folder contains Elasticsearch
-{ref}/ingest.html[Ingest Node] pipeline configurations. The Ingest
-Node pipelines are responsible for parsing the log lines and doing other
-manipulations on the data.
+The `ingest/` folder contains {es} {ref}/ingest.html[ingest pipeline]
+configurations. Ingest pipelines are responsible for parsing the log lines and
+doing other manipulations on the data.
 
 The files in this folder are JSON or YAML documents representing
 {ref}/pipeline.html[pipeline definitions]. Just like with the `config/`
@@ -344,10 +343,10 @@ on_failure:
 ----
 
 From here, you would typically add processors to the `processors` array to do
-the actual parsing. For details on how to use ingest node processors, see the
-{ref}/ingest-processors.html[ingest node documentation]. In
+the actual parsing. For information about available ingest processors, see the
+{ref}/processors.html[processor reference documentation]. In
 particular, you will likely find the
-{ref}/grok-processor.html[Grok processor] to be useful for parsing.
+{ref}/grok-processor.html[grok processor] to be useful for parsing.
 Here is an example for parsing the Nginx access logs.
 
 [source,json]

diff --git a/filebeat/_meta/config/filebeat.inputs.reference.yml.tmpl b/filebeat/_meta/config/filebeat.inputs.reference.yml.tmpl
@@ -168,7 +168,7 @@ filebeat.inputs:
   # this can mean that the first entries of a new file are skipped.
   #tail_files: false
 
-  # The Ingest Node pipeline ID associated with this input. If this is set, it
+  # The ingest pipeline ID associated with this input. If this is set, it
   # overwrites the pipeline option from the Elasticsearch output.
   #pipeline:
 
@@ -351,7 +351,7 @@ filebeat.inputs:
   # carriage_return, carriage_return_line_feed, next_line, line_separator, paragraph_separator.
   #line_terminator: auto
 
-  # The Ingest Node pipeline ID associated with this input. If this is set, it
+  # The ingest pipeline ID associated with this input. If this is set, it
   # overwrites the pipeline option from the Elasticsearch output.
   #pipeline:
 

diff --git a/filebeat/beater/filebeat.go b/filebeat/beater/filebeat.go
@@ -58,9 +58,9 @@ import (
 	_ "github.com/elastic/beats/v7/filebeat/autodiscover"
 )
 
-const pipelinesWarning = "Filebeat is unable to load the Ingest Node pipelines for the configured" +
+const pipelinesWarning = "Filebeat is unable to load the ingest pipelines for the configured" +
 	" modules because the Elasticsearch output is not configured/enabled. If you have" +
-	" already loaded the Ingest Node pipelines or are using Logstash pipelines, you" +
+	" already loaded the ingest pipelines or are using Logstash pipelines, you" +
 	" can ignore this warning."
 
 var (

diff --git a/filebeat/docs/filebeat-modules-options.asciidoc b/filebeat/docs/filebeat-modules-options.asciidoc
@@ -13,7 +13,7 @@ a log type that isn't supported, or you want to use a different setup.
 
 {beatname_uc} <<{beatname_lc}-modules,modules>> provide a quick way to
 get started processing common log formats. They contain default configurations,
-{es} ingest node pipeline definitions, and {kib} dashboards to help you
+{es} ingest pipeline definitions, and {kib} dashboards to help you
 implement and deploy a log monitoring solution.
 
 You can configure modules in the `modules.d` directory (recommended), or in the

diff --git a/filebeat/docs/include/what-happens.asciidoc b/filebeat/docs/include/what-happens.asciidoc
@@ -5,8 +5,8 @@ defaults)
 
 * Makes sure each multiline log event gets sent as a single event
 
-* Uses ingest node to parse and process the log lines, shaping the data into a structure suitable
-for visualizing in Kibana
+* Uses an {es} ingest pipeline to parse and process the log lines, shaping the
+data into a structure suitable for visualizing in Kibana
 
 ifeval::["{has-dashboards}"=="true"]
 * Deploys dashboards for visualizing the log data

diff --git a/filebeat/docs/inputs/input-common-options.asciidoc b/filebeat/docs/inputs/input-common-options.asciidoc
@@ -77,7 +77,7 @@ processors in your config.
 [float]
 ===== `pipeline`
 
-The Ingest Node pipeline ID to set for the events generated by this input.
+The ingest pipeline ID to set for the events generated by this input.
 
 NOTE: The pipeline ID can also be configured in the Elasticsearch output, but
 this option usually results in simpler configuration files. If the pipeline is

diff --git a/filebeat/docs/modules-overview.asciidoc b/filebeat/docs/modules-overview.asciidoc
@@ -13,7 +13,7 @@ the following:
   The {beatname_uc} configuration is also responsible with stitching together
   multiline events when needed.
 
-* {es} {ref}/ingest.html[Ingest Node] pipeline definition,
+* {es} {ref}/ingest.html[ingest pipeline] definition,
   which is used to parse the log lines.
 
 * Fields definitions, which are used to configure {es} with the

diff --git a/filebeat/docs/modules/iptables.asciidoc b/filebeat/docs/modules/iptables.asciidoc
@@ -22,8 +22,8 @@ When you run the module, it performs a few tasks under the hood:
 * Sets the default input to `syslog` and binds to `localhost` port `9001`
   (but don’t worry, you can override the defaults).
 
-* Uses ingest node to parse and process the log lines, shaping the data into
-  a structure suitable for visualizing in Kibana.
+* Uses an ingest pipeline to parse and process the log lines, shaping the data
+  into a structure suitable for visualizing in Kibana.
 
 * Deploys dashboards for visualizing the log data.
 

diff --git a/filebeat/docs/modules/netflow.asciidoc b/filebeat/docs/modules/netflow.asciidoc
@@ -18,7 +18,7 @@ NetFlow versions older than 9, fields are mapped automatically to NetFlow v9.
 
 This module wraps the <<filebeat-input-netflow,netflow input>> to enrich the
 flow records with geolocation information about the IP endpoints by using
-Elasticsearch Ingest Node.
+an {es} ingest pipeline.
 
 include::../include/gs-link.asciidoc[]
 

diff --git a/filebeat/filebeat.reference.yml b/filebeat/filebeat.reference.yml
@@ -575,7 +575,7 @@ filebeat.inputs:
   # this can mean that the first entries of a new file are skipped.
   #tail_files: false
 
-  # The Ingest Node pipeline ID associated with this input. If this is set, it
+  # The ingest pipeline ID associated with this input. If this is set, it
   # overwrites the pipeline option from the Elasticsearch output.
   #pipeline:
 
@@ -758,7 +758,7 @@ filebeat.inputs:
   # carriage_return, carriage_return_line_feed, next_line, line_separator, paragraph_separator.
   #line_terminator: auto
 
-  # The Ingest Node pipeline ID associated with this input. If this is set, it
+  # The ingest pipeline ID associated with this input. If this is set, it
   # overwrites the pipeline option from the Elasticsearch output.
   #pipeline:
 
@@ -1391,7 +1391,7 @@ output.elasticsearch:
   # In case you modify this pattern you must update setup.template.name and setup.template.pattern accordingly.
   #index: "filebeat-%{[agent.version]}-%{+yyyy.MM.dd}"
 
-  # Optional ingest node pipeline. By default no pipeline will be used.
+  # Optional ingest pipeline. By default no pipeline will be used.
   #pipeline: ""
 
   # Optional HTTP path
-Original file line number
+Diff line change
@@ Expand Up / @@ -2358,7 +2358,7 @@ alias to: error.message @@
     [float]
     === geoip
-    The geoip fields are defined as a convenience in case you decide to enrich the data using a geoip filter in Logstash or Ingest Node.
+    The geoip fields are defined as a convenience in case you decide to enrich the data using a geoip filter in Logstash or an Elasticsearch geoip ingest processor.
@@ Expand Down @@