Ingest pipelines preprocess and enrich APM documents before indexing them. For example, a pipeline might define one processor that removes a field, and another that renames a field. This can be useful for ensuring data security by removing or obfuscating sensitive information. See data security for more on this topic.
The default APM pipelines are defined in index templates that Fleet loads into Elasticsearch. Elasticsearch then uses the index pattern in these index templates to match pipelines to APM data streams.
View ingest pipelinesedit
To view or edit a default pipelines in Kibana,
select Stack Management > Ingest Pipelines.
It is not currently possible to edit or add pipelines that persist through upgrades.
See ingest node pipelines for more information.