# Filebeat's stdin harvester\_buffer\_size leads to not processing messages

**URL:** <https://discuss.elastic.co/t/filebeats-stdin-harvester-buffer-size-leads-to-not-processing-messages/289597>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [November 18, 2021, 1:31pm UTC](https://discuss.elastic.co/t/filebeats-stdin-harvester-buffer-size-leads-to-not-processing-messages/289597 "2021-11-18T13:31:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![djmcgreal-cc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/djmcgreal-cc/32/85463_2.png) [@djmcgreal-cc](https://discuss.elastic.co/u/djmcgreal-cc)\
**Post date:** [November 18, 2021, 1:31pm UTC](https://discuss.elastic.co/t/filebeats-stdin-harvester-buffer-size-leads-to-not-processing-messages/289597/1 "2021-11-18T13:31:29Z")

</div>

I'd like to read from stdin to filebeat. It's in JSONL with `json` set on the stdin input.

When I send a single message of about 1600 bytes nothing gets processed, even if I ask the filebeat process to quit. I can get things processed if I send multiple messages, seemingly ~9 or 10 at a time get batched.

I worry that messages will sit in the harvester's buffer long-term if there's no further messages and that messages are lost during shutdowns.

---

<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:** [December 16, 2021, 3:31pm UTC](https://discuss.elastic.co/t/filebeats-stdin-harvester-buffer-size-leads-to-not-processing-messages/289597/2 "2021-12-16T15:31:44Z")

</div>

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