# Filebeat limit processing events

**URL:** <https://discuss.elastic.co/t/filebeat-limit-processing-events/313485>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [September 1, 2022, 9:15pm UTC](https://discuss.elastic.co/t/filebeat-limit-processing-events/313485 "2022-09-01T21:15:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![amandagmsd](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@amandagmsd](https://discuss.elastic.co/u/amandagmsd)\
**Post date:** [September 1, 2022, 9:16pm UTC](https://discuss.elastic.co/t/filebeat-limit-processing-events/313485/1 "2022-09-01T21:16:00Z")

</div>

Hi,

Is there a way to increase the number of processing events of filebeat?

Example:  
I have a configuration for filebeat to read aws cloudwatch logs, but the biggest number that is on log debug is 100 for processing events. Can this number be bigger?

```auto
{"log.level":"debug","@timestamp":"2022-09-01T20:29:01.095Z","log.logger":"input.aws-cloudwatch.cloudwatch_poller","log.origin":{"file.name":"awscloudwatch/cloudwatch.go","file.line":91},"message":"Processing #100 events","service.name":"filebeat","id":"C52EF21AD91C78FC","ecs.version":"1.6.0"}

```

See "message" above.

---

<div class="post-metadata">

**Author:** ![amandagmsd](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@amandagmsd](https://discuss.elastic.co/u/amandagmsd)\
**Post date:** [September 5, 2022, 1:32pm UTC](https://discuss.elastic.co/t/filebeat-limit-processing-events/313485/2 "2022-09-05T13:32:11Z")

</div>

Hi, could anyone help me with this issue?  
Thank you

---

<div class="post-metadata">

**Author:** ![mtojek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mtojek/32/63863_2.png) [@mtojek](https://discuss.elastic.co/u/mtojek)\
**Post date:** [September 5, 2022, 2:42pm UTC](https://discuss.elastic.co/t/filebeat-limit-processing-events/313485/3 "2022-09-05T14:42:00Z")

</div>

Does it look like the issue you described? [[Filebeat] Make limit argument configurable in AWS CloudWatch input · Issue #32932 · elastic/beats · GitHub](https://github.com/elastic/beats/issues/32932)

---

<div class="post-metadata">

**Author:** ![amandagmsd](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@amandagmsd](https://discuss.elastic.co/u/amandagmsd)\
**Post date:** [September 6, 2022, 7:08pm UTC](https://discuss.elastic.co/t/filebeat-limit-processing-events/313485/4 "2022-09-06T19:08:16Z")

</div>

Hi Marcin,  
Yes, it's the same issue.  
Is there an estimate of when it will be ready?

---

<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:** [October 4, 2022, 9:09pm UTC](https://discuss.elastic.co/t/filebeat-limit-processing-events/313485/5 "2022-10-04T21:09:06Z")

</div>

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