# Tips for managing spikes in data sources

**URL:** <https://discuss.elastic.co/t/tips-for-managing-spikes-in-data-sources/373143>\
**Category:** Elasticsearch\
**Created:** [January 13, 2025, 9:27pm UTC](https://discuss.elastic.co/t/tips-for-managing-spikes-in-data-sources/373143 "2025-01-13T21:27:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![erikg](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@erikg](https://discuss.elastic.co/u/erikg)\
**Post date:** [January 13, 2025, 9:27pm UTC](https://discuss.elastic.co/t/tips-for-managing-spikes-in-data-sources/373143/1 "2025-01-13T21:27:12Z")

</div>

Hello,

I was wondering what others do to manage a huge increase in events from a particular data source (spikes). I know there's a rate lime processor on elastic agent but is there other mechanisms used?

I have heard of using Kafka to handle this kind of approach but wouldn't Kafka lead to make data less real time in Elastic?