# Filebeat - elasticsearch output without pipeline management

**URL:** <https://discuss.elastic.co/t/filebeat-elasticsearch-output-without-pipeline-management/337322>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [June 30, 2023, 2:30pm UTC](https://discuss.elastic.co/t/filebeat-elasticsearch-output-without-pipeline-management/337322 "2023-06-30T14:30:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon68795679](https://avatars.discourse-cdn.com/v4/letter/a/a587f6/32.png) [@anon68795679](https://discuss.elastic.co/u/anon68795679)\
**Post date:** [June 30, 2023, 2:30pm UTC](https://discuss.elastic.co/t/filebeat-elasticsearch-output-without-pipeline-management/337322/1 "2023-06-30T14:30:32Z")

</div>

Hi,

we want to deliver PostgresSQL logs with the filebeat postgres module to an elasticsearch output.  
But the filebeat shouldn't manage anything in the elasticsearch. ILM, template and ingest pipelines are managed by other systems.  
So the elasticsearch user which is used by filebeat has only write permissions for the index.

The issue is that filebeat tries to put the (already existing) ingest pipeline to Elasticsearch before writing the log document.

Is it possible to disable this?

Regards,  
Marcel

---

<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 28, 2023, 4:31pm UTC](https://discuss.elastic.co/t/filebeat-elasticsearch-output-without-pipeline-management/337322/2 "2023-07-28T16:31:20Z")

</div>

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