Enriching data with a custom ingest pipeline for an existing Elastic Agent integration
As we saw in the previous recipe, ingest pipelines are instrumental for data transformation and enrichment. They can be used independently, or you can define a pipeline in the settings of an index so that each incoming document to this index passes through the specified pipeline. In this recipe, we’ll examine how to leverage a custom pipeline to enrich documents generated by an integration.
Getting ready
You’ll need an up-and-running Elastic deployment with Elasticsearch, Kibana, and Fleet Server.
Make sure to have implemented the previous recipe: Creating an ingest pipeline.
How to do it...
As mentioned, we’ll use the ingest pipeline created in the previous recipe:
- Head to Kibana | Fleet | Agent Policies.
- Select the policy running the Apache HTTP Server integration.
- Click on Edit Integration on the right side of the integration.
- Under the Apache...
