# Throughput tweaks for Elastic Agent Integrations? Agent integration not able to keep up with volume of events within an Eventhub

**URL:** <https://discuss.elastic.co/t/throughput-tweaks-for-elastic-agent-integrations-agent-integration-not-able-to-keep-up-with-volume-of-events-within-an-eventhub/344515>\
**Category:** Elastic Agent\
**Created:** [October 6, 2023, 3:17am UTC](https://discuss.elastic.co/t/throughput-tweaks-for-elastic-agent-integrations-agent-integration-not-able-to-keep-up-with-volume-of-events-within-an-eventhub/344515 "2023-10-06T03:17:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![elasticnub](https://avatars.discourse-cdn.com/v4/letter/e/b9e5f3/32.png) [@elasticnub](https://discuss.elastic.co/u/elasticnub)\
**Post date:** [October 6, 2023, 3:17am UTC](https://discuss.elastic.co/t/throughput-tweaks-for-elastic-agent-integrations-agent-integration-not-able-to-keep-up-with-volume-of-events-within-an-eventhub/344515/1 "2023-10-06T03:17:32Z")

</div>

We are having issues with the agent being able to support roughly ~80GB a day of M365 event data ingestion being pulled from an EventHub. The aggregation server is by no means pegged on any resources so I am trying to figure out any tweaks to allow for higher throughput.

---

<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:** [November 3, 2023, 3:18am UTC](https://discuss.elastic.co/t/throughput-tweaks-for-elastic-agent-integrations-agent-integration-not-able-to-keep-up-with-volume-of-events-within-an-eventhub/344515/2 "2023-11-03T03:18:01Z")

</div>

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