# Increasing queue size

**URL:** <https://discuss.elastic.co/t/increasing-queue-size/294520>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [January 17, 2022, 3:25am UTC](https://discuss.elastic.co/t/increasing-queue-size/294520 "2022-01-17T03:25:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hjazz6](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hjazz6/32/79007_2.png) [@hjazz6](https://discuss.elastic.co/u/hjazz6)\
**Post date:** [January 17, 2022, 3:25am UTC](https://discuss.elastic.co/t/increasing-queue-size/294520/1 "2022-01-17T03:25:34Z")

</div>

Hi,

I'm ingesting Netflow data using Filebeat 7.14.0 and writing the output into Elasticsearch. I'm trying to tweak the various configuration settings in order to improve the performance (currently, it seems like filebeat/ES cannot handle the incoming load.)

I see from the filebeat monitoring logs that `libbeat.pipeline.queue.max_events: 4096`. I wanted to increase this to see if the performance would improve.

My `filebeat.yml` contains only the `filebeat.config.modules` section, while the `filebeat.inputs` are effectively not enabled.

My `netflow.yml` is as follows.

```auto
- module: netflow
  log:
    enabled: true
    var:
      netflow_host: 0.0.0.0
      netflow.port: 1234
      queue_size: 8192

```

I'm not sure if setting `queue_size: 8192` in `netflow.yml` is helping because I don't see this anywhere on the filebeat monitoring log, and `libbeat.pipeline.queue.max_events` remains at `4096` despite multiple restarts of filebeat.

Where do I configure `libbeat.pipeline.queue.max_events`?

Thank you.

---

<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:** [February 14, 2022, 5:25am UTC](https://discuss.elastic.co/t/increasing-queue-size/294520/2 "2022-02-14T05:25:52Z")

</div>

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