# Using a custom ingest pipeline with a module

**URL:** <https://discuss.elastic.co/t/using-a-custom-ingest-pipeline-with-a-module/239143>\
**Category:** Elasticsearch\
**Created:** [June 29, 2020, 3:30pm UTC](https://discuss.elastic.co/t/using-a-custom-ingest-pipeline-with-a-module/239143 "2020-06-29T15:30:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamiejackson](https://avatars.discourse-cdn.com/v4/letter/j/d07c76/32.png) [@jamiejackson](https://discuss.elastic.co/u/jamiejackson)\
**Post date:** [June 29, 2020, 3:30pm UTC](https://discuss.elastic.co/t/using-a-custom-ingest-pipeline-with-a-module/239143/1 "2020-06-29T15:30:45Z")

</div>

Picking back up on a topic that I shelved a while back: [Apache HTTPD logs with (comma-delimited) X-Forwarded-For IPs](https://discuss.elastic.co/t/apache-httpd-logs-with-comma-delimited-x-forwarded-for-ips/181917)

@jsoriano had been helping me and suggested that I try the following to invoke a custom ingest pipeline:

```auto
filebeat.modules:
  - module: apache
    access:
      input:
        pipeline: apache_with_x_forwarded_for
        paths: ["/var/log/apache2/access*"]
    error:
      var.paths: ["/var/log/apache2/error*"]

```

Unfortunately, that doesn't _seem_ to have any effect on the pipeline used, since it still seems to be using the stock one (none of my changes are reflected in the indexed data).

Any suggestions as to the best path forward?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 27, 2020, 3:31pm UTC](https://discuss.elastic.co/t/using-a-custom-ingest-pipeline-with-a-module/239143/2 "2020-07-27T15:31:07Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.