# Elastic Agent cuts the number of logs in the output

**URL:** <https://discuss.elastic.co/t/elastic-agent-cuts-the-number-of-logs-in-the-output/364823>\
**Category:** Elastic Agent\
**Tags:** filebeat\
**Created:** [August 13, 2024, 10:00am UTC](https://discuss.elastic.co/t/elastic-agent-cuts-the-number-of-logs-in-the-output/364823 "2024-08-13T10:00:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Patryk\_Ostrowski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patryk_ostrowski/32/111965_2.png) [@Patryk\_Ostrowski](https://discuss.elastic.co/u/Patryk_Ostrowski)\
**Post date:** [August 13, 2024, 10:00am UTC](https://discuss.elastic.co/t/elastic-agent-cuts-the-number-of-logs-in-the-output/364823/1 "2024-08-13T10:00:41Z")

</div>

Hello, I have a problem with elastic agent, the problem also repeats when using filebeat. There are about 70k logs per second coming to the interface (each packet is a separate log for SRX). On the other hand, the agent writes to elastica only about 8 thousand logs for a second. In the fleet policy configuration, I increased the number of concurrent processing to 8 CPUs, but it did not change anything. Can I ask for guidance on this problem?

`Average: IFACE rxpck/s txpck/s rxkB/s txkB/s rxcmp/s txcmp/s rxmcst/s %ifutil 09:56:48 AM ens35 71429.00 0.00 100947.09 0.00 0.00 0.00 0.00 8.27`