All methods and paths for this operation:
Get information about one or more ingest pipelines. This API returns a local reference of the pipeline.
Path parameters
-
Comma-separated list of pipeline IDs to retrieve. Wildcard (
*) expressions are supported. To get all ingest pipelines, omit this parameter or use*.
Query parameters
-
Period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error.
External documentation -
Return pipelines without their definitions
Responses
-
Hide response attribute Show response attribute object
-
Hide * attributes Show * attributes object
-
Description of the ingest pipeline.
-
Processors to run immediately after a processor failure.
Hide on_failure attributes Show on_failure attributes object
-
Appends one or more values to an existing array if the field already exists and it is an array. Converts a scalar to an array and appends one or more values to it if the field exists and it is a scalar. Creates an array containing the provided values if the field doesn’t exist. Accepts a single value or an array of values.
-
The attachment processor lets Elasticsearch extract file attachments in common formats (such as PPT, XLS, and PDF) by using the Apache text extraction library Tika.
-
Converts a human readable byte value (for example
1kb) to its value in bytes (for example1024). If the field is an array of strings, all members of the array will be converted. Supported human readable units are "b", "kb", "mb", "gb", "tb", "pb" case insensitive. An error will occur if the field is not a supported format or resultant value exceeds 263. -
Converts a CEF message into a structured format.
-
Converts circle definitions of shapes to regular polygons which approximate them.
-
Computes the Community ID for network flow data as defined in the Community ID Specification. You can use a community ID to correlate network events related to a single flow.
-
Converts a field in the currently ingested document to a different type, such as converting a string to an integer. If the field value is an array, all members will be converted.
-
Extracts fields from CSV line out of a single text field within a document. Any empty field in CSV will be skipped.
-
Parses dates from fields, and then uses the date or timestamp as the timestamp for the document.
-
The purpose of this processor is to point documents to the right time based index based on a date or timestamp field in a document by using the date math index name support.
-
Extracts structured fields out of a single text field by matching the text field against a delimiter-based pattern.
-
Expands a field with dots into an object field. This processor allows fields with dots in the name to be accessible by other processors in the pipeline. Otherwise these fields can’t be accessed by any processor.
-
Drops the document without raising any errors. This is useful to prevent the document from getting indexed based on some condition.
-
The
enrichprocessor can enrich documents with data from another index. -
Raises an exception. This is useful for when you expect a pipeline to fail and want to relay a specific message to the requester.
-
Computes a hash of the document’s content. You can use this hash for content fingerprinting.
-
Runs an ingest processor on each element of an array or object.
-
Currently an undocumented alias for GeoIP Processor.
-
Converts geo-grid definitions of grid tiles or cells to regular bounding boxes or polygons which describe their shape. This is useful if there is a need to interact with the tile shapes as spatially indexable fields.
-
The
geoipprocessor adds information about the geographical location of an IPv4 or IPv6 address. -
Extracts structured fields out of a single text field within a document. You choose which field to extract matched fields from, as well as the grok pattern you expect will match. A grok pattern is like a regular expression that supports aliased expressions that can be reused.
-
Converts a string field by applying a regular expression and a replacement. If the field is an array of string, all members of the array will be converted. If any non-string values are encountered, the processor will throw an exception.
-
Removes HTML tags from the field. If the field is an array of strings, HTML tags will be removed from all members of the array.
-
Uses a pre-trained data frame analytics model or a model deployed for natural language processing tasks to infer against the data that is being ingested in the pipeline.
-
Joins each element of an array into a single string using a separator character between each element. Throws an error when the field is not an array.
-
Parses a string containing JSON data into a structured object, string, or other value.
-
This processor helps automatically parse messages (or specific event fields) which are of the
foo=barvariety. -
Converts a string to its lowercase equivalent. If the field is an array of strings, all members of the array will be converted.
-
Calculates the network direction given a source IP address, destination IP address, and a list of internal networks.
-
Executes another pipeline.
-
The Redact processor uses the Grok rules engine to obscure text in the input document matching the given Grok patterns. The processor can be used to obscure Personal Identifying Information (PII) by configuring it to detect known patterns such as email or IP addresses. Text that matches a Grok pattern is replaced with a configurable string such as
<EMAIL>where an email address is matched or simply replace all matches with the text<REDACTED>if preferred. -
Extracts the registered domain (also known as the effective top-level domain or eTLD), sub-domain, and top-level domain from a fully qualified domain name (FQDN). Uses the registered domains defined in the Mozilla Public Suffix List.
-
Removes existing fields. If one field doesn’t exist, an exception will be thrown.
-
Renames an existing field. If the field doesn’t exist or the new name is already used, an exception will be thrown.
-
Routes a document to another target index or data stream. When setting the
destinationoption, the target is explicitly specified and the dataset and namespace options can’t be set. When thedestinationoption is not set, this processor is in a data stream mode. Note that in this mode, the reroute processor can only be used on data streams that follow the data stream naming scheme. -
Runs an inline or stored script on incoming documents. The script runs in the
ingestcontext. -
Adds a field with the specified value. If the field already exists, its value will be replaced with the provided one.
-
Sets user-related details (such as
username,roles,email,full_name,metadata,api_key,realmandauthentication_type) from the current authenticated user to the current document by pre-processing the ingest. -
Sorts the elements of an array ascending or descending. Homogeneous arrays of numbers will be sorted numerically, while arrays of strings or heterogeneous arrays of strings + numbers will be sorted lexicographically. Throws an error when the field is not an array.
-
Splits a field into an array using a separator character. Only works on string fields.
-
Terminates the current ingest pipeline, causing no further processors to be run. This will normally be executed conditionally, using the
ifoption. -
Trims whitespace from a field. If the field is an array of strings, all members of the array will be trimmed. This only works on leading and trailing whitespace.
-
Converts a string to its uppercase equivalent. If the field is an array of strings, all members of the array will be converted.
-
URL-decodes a string. If the field is an array of strings, all members of the array will be decoded.
-
Parses a Uniform Resource Identifier (URI) string and extracts its components as an object. This URI object includes properties for the URI’s domain, path, fragment, port, query, scheme, user info, username, and password.
-
The
user_agentprocessor extracts details from the user agent string a browser sends with its web requests. This processor adds this information by default under theuser_agentfield.
-
-
Processors used to perform transformations on documents before indexing. Processors run sequentially in the order specified.
Hide processors attributes Show processors attributes object
-
Appends one or more values to an existing array if the field already exists and it is an array. Converts a scalar to an array and appends one or more values to it if the field exists and it is a scalar. Creates an array containing the provided values if the field doesn’t exist. Accepts a single value or an array of values.
-
The attachment processor lets Elasticsearch extract file attachments in common formats (such as PPT, XLS, and PDF) by using the Apache text extraction library Tika.
-
Converts a human readable byte value (for example
1kb) to its value in bytes (for example1024). If the field is an array of strings, all members of the array will be converted. Supported human readable units are "b", "kb", "mb", "gb", "tb", "pb" case insensitive. An error will occur if the field is not a supported format or resultant value exceeds 263. -
Converts a CEF message into a structured format.
-
Converts circle definitions of shapes to regular polygons which approximate them.
-
Computes the Community ID for network flow data as defined in the Community ID Specification. You can use a community ID to correlate network events related to a single flow.
-
Converts a field in the currently ingested document to a different type, such as converting a string to an integer. If the field value is an array, all members will be converted.
-
Extracts fields from CSV line out of a single text field within a document. Any empty field in CSV will be skipped.
-
Parses dates from fields, and then uses the date or timestamp as the timestamp for the document.
-
The purpose of this processor is to point documents to the right time based index based on a date or timestamp field in a document by using the date math index name support.
-
Extracts structured fields out of a single text field by matching the text field against a delimiter-based pattern.
-
Expands a field with dots into an object field. This processor allows fields with dots in the name to be accessible by other processors in the pipeline. Otherwise these fields can’t be accessed by any processor.
-
Drops the document without raising any errors. This is useful to prevent the document from getting indexed based on some condition.
-
The
enrichprocessor can enrich documents with data from another index. -
Raises an exception. This is useful for when you expect a pipeline to fail and want to relay a specific message to the requester.
-
Computes a hash of the document’s content. You can use this hash for content fingerprinting.
-
Runs an ingest processor on each element of an array or object.
-
Currently an undocumented alias for GeoIP Processor.
-
Converts geo-grid definitions of grid tiles or cells to regular bounding boxes or polygons which describe their shape. This is useful if there is a need to interact with the tile shapes as spatially indexable fields.
-
The
geoipprocessor adds information about the geographical location of an IPv4 or IPv6 address. -
Extracts structured fields out of a single text field within a document. You choose which field to extract matched fields from, as well as the grok pattern you expect will match. A grok pattern is like a regular expression that supports aliased expressions that can be reused.
-
Converts a string field by applying a regular expression and a replacement. If the field is an array of string, all members of the array will be converted. If any non-string values are encountered, the processor will throw an exception.
-
Removes HTML tags from the field. If the field is an array of strings, HTML tags will be removed from all members of the array.
-
Uses a pre-trained data frame analytics model or a model deployed for natural language processing tasks to infer against the data that is being ingested in the pipeline.
-
Joins each element of an array into a single string using a separator character between each element. Throws an error when the field is not an array.
-
Parses a string containing JSON data into a structured object, string, or other value.
-
This processor helps automatically parse messages (or specific event fields) which are of the
foo=barvariety. -
Converts a string to its lowercase equivalent. If the field is an array of strings, all members of the array will be converted.
-
Calculates the network direction given a source IP address, destination IP address, and a list of internal networks.
-
Executes another pipeline.
-
The Redact processor uses the Grok rules engine to obscure text in the input document matching the given Grok patterns. The processor can be used to obscure Personal Identifying Information (PII) by configuring it to detect known patterns such as email or IP addresses. Text that matches a Grok pattern is replaced with a configurable string such as
<EMAIL>where an email address is matched or simply replace all matches with the text<REDACTED>if preferred. -
Extracts the registered domain (also known as the effective top-level domain or eTLD), sub-domain, and top-level domain from a fully qualified domain name (FQDN). Uses the registered domains defined in the Mozilla Public Suffix List.
-
Removes existing fields. If one field doesn’t exist, an exception will be thrown.
-
Renames an existing field. If the field doesn’t exist or the new name is already used, an exception will be thrown.
-
Routes a document to another target index or data stream. When setting the
destinationoption, the target is explicitly specified and the dataset and namespace options can’t be set. When thedestinationoption is not set, this processor is in a data stream mode. Note that in this mode, the reroute processor can only be used on data streams that follow the data stream naming scheme. -
Runs an inline or stored script on incoming documents. The script runs in the
ingestcontext. -
Adds a field with the specified value. If the field already exists, its value will be replaced with the provided one.
-
Sets user-related details (such as
username,roles,email,full_name,metadata,api_key,realmandauthentication_type) from the current authenticated user to the current document by pre-processing the ingest. -
Sorts the elements of an array ascending or descending. Homogeneous arrays of numbers will be sorted numerically, while arrays of strings or heterogeneous arrays of strings + numbers will be sorted lexicographically. Throws an error when the field is not an array.
-
Splits a field into an array using a separator character. Only works on string fields.
-
Terminates the current ingest pipeline, causing no further processors to be run. This will normally be executed conditionally, using the
ifoption. -
Trims whitespace from a field. If the field is an array of strings, all members of the array will be trimmed. This only works on leading and trailing whitespace.
-
Converts a string to its uppercase equivalent. If the field is an array of strings, all members of the array will be converted.
-
URL-decodes a string. If the field is an array of strings, all members of the array will be decoded.
-
Parses a Uniform Resource Identifier (URI) string and extracts its components as an object. This URI object includes properties for the URI’s domain, path, fragment, port, query, scheme, user info, username, and password.
-
The
user_agentprocessor extracts details from the user agent string a browser sends with its web requests. This processor adds this information by default under theuser_agentfield.
-
-
Version number used by external systems to track ingest pipelines.
-
Marks this ingest pipeline as deprecated. When a deprecated ingest pipeline is referenced as the default or final pipeline when creating or updating a non-deprecated index template, Elasticsearch will emit a deprecation warning.
Default value is
false. -
Arbitrary metadata about the ingest pipeline. This map is not automatically generated by Elasticsearch.
-
Date and time when the pipeline was created, in milliseconds since the epoch.
-
Date and time when the pipeline was last modified, in milliseconds since the epoch.
-
Controls how processors in this pipeline should read and write data on a document's source.
Values are
classicorflexible.
-
-
GET /_ingest/pipeline/my-pipeline-id
resp = client.ingest.get_pipeline(
id="my-pipeline-id",
)const response = await client.ingest.getPipeline({
id: "my-pipeline-id",
});response = client.ingest.get_pipeline(
id: "my-pipeline-id"
)$resp = $client->ingest()->getPipeline([
"id" => "my-pipeline-id",
]);curl -X GET -H "Authorization: ApiKey $ELASTIC_API_KEY" "$ELASTICSEARCH_URL/_ingest/pipeline/my-pipeline-id"client.ingest().getPipeline(g -> g
.id("my-pipeline-id")
);
{
"my-pipeline-id" : {
"description" : "describe pipeline",
"version" : 123,
"processors" : [
{
"set" : {
"field" : "foo",
"value" : "bar"
}
}
],
"created_date" : "2024-01-01T12:00:00.000Z",
"created_date_millis" : 1704110400000,
"modified_date" : "2025-01-01T12:00:00.000Z",
"modified_date_millis" : 1735732800000
}
}