# Ingest Pipeline does not update on filebeat setup

**URL:** https://discuss.elastic.co/t/ingest-pipeline-does-not-update-on-filebeat-setup/142769
**Category:** Beats
**Tags:** filebeat
**Created:** [August 2, 2018, 1:09pm UTC](https://discuss.elastic.co/t/ingest-pipeline-does-not-update-on-filebeat-setup/142769 "2018-08-02T13:09:58Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Tethik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tethik/32/34017_2.png) [@Tethik](https://discuss.elastic.co/u/Tethik)
#### Post date: [August 2, 2018, 1:09pm UTC](https://discuss.elastic.co/t/ingest-pipeline-does-not-update-on-filebeat-setup/142769/1 "2018-08-02T13:09:58Z")

</div>

I'm trying to develop two new modules for filebeat, but ran into issues as I was trying to update my pipelines after some trial and error. It seems like they don't update like they should, so this could be a potential issue in filebeat.

A [previous topic](https://discuss.elastic.co/t/ingest-pipeline-is-not-updated-on-module-changes/138029) suggested running `filebeat setup`. I did this, but had no effect.

The [create a module tutorial](https://www.elastic.co/guide/en/beats/devguide/current/filebeat-modules-devguide.html) also suggests running `filebeat setup --pipelines` to force the update, but this also made no difference.

I managed to get my updated pipelines and get my modules working eventually by manually sending the pipeline via the dev console in kibana ([using the ingest api](https://www.elastic.co/guide/en/elasticsearch/reference/current/put-pipeline-api.html)).

Version: 6.3.2 (based off the 6.3.2 tag on github repo).

---

<div class="post-metadata">

### Author: ![kvch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kvch/32/72058_2.png) [@kvch](https://discuss.elastic.co/u/kvch)
#### Post date: [August 2, 2018, 1:35pm UTC](https://discuss.elastic.co/t/ingest-pipeline-does-not-update-on-filebeat-setup/142769/2 "2018-08-02T13:35:50Z")

</div>

Pipelines of enabled modules are loaded only by Filebeat. Have you enabled you module in the config or during setup?

You could run:

```auto
./filebeat setup -pipelines -modules="{{ your-module-name }}"

```

---

<div class="post-metadata">

### Author: ![Tethik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tethik/32/34017_2.png) [@Tethik](https://discuss.elastic.co/u/Tethik)
#### Post date: [August 2, 2018, 1:42pm UTC](https://discuss.elastic.co/t/ingest-pipeline-does-not-update-on-filebeat-setup/142769/3 "2018-08-02T13:42:06Z")

</div>

Thanks for the quick reply!

I tried it in the config, but on a server where the module was enabled in a `/etc/filebeat/modules.d/` directory. I did load a config locally too, to talk with my elasticsearch instance, but did not try explicitly enabling the module. I'll try it.

---

<div class="post-metadata">

### Author: ![Tethik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tethik/32/34017_2.png) [@Tethik](https://discuss.elastic.co/u/Tethik)
#### Post date: [August 2, 2018, 2:27pm UTC](https://discuss.elastic.co/t/ingest-pipeline-does-not-update-on-filebeat-setup/142769/4 "2018-08-02T14:27:59Z")

</div>

It worked! I think my error then was not explicitly enabling the new modules via the `-modules` option.

---

<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: [August 30, 2018, 2:37pm UTC](https://discuss.elastic.co/t/ingest-pipeline-does-not-update-on-filebeat-setup/142769/5 "2018-08-30T14:37:49Z")

</div>

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