# Custom UDP Logs

**URL:** <https://discuss.elastic.co/t/custom-udp-logs/328867>\
**Category:** Elastic Agent\
**Created:** [March 29, 2023, 9:10pm UTC](https://discuss.elastic.co/t/custom-udp-logs/328867 "2023-03-29T21:10:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Thomas\_Baumann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomas_baumann/32/118921_2.png) [@Thomas\_Baumann](https://discuss.elastic.co/u/Thomas_Baumann)\
**Post date:** [March 29, 2023, 9:10pm UTC](https://discuss.elastic.co/t/custom-udp-logs/328867/1 "2023-03-29T21:10:47Z")

</div>

Hello,

we are using an Fleet Server, including Custom UDP logs integration. We observed an issue with data are not ingested with a load about 500 EPS. About 30% to 50 % messages are not ingested.

Also netstat -ulpn shows that the receive queue is quite high:

udp 116480 0 127.0.0.1:1514 0.0.0.0:\* 726338/filebeat

CPU and Memory usage is low, also no IO issues detected. Does somebody uses this integration successfull in production environments ? With an acceptable processing rate ?

We switched back to some more mature implementation, logstash directly to elasticsearch. We reached about 5000 eps without any issues.

Would be great that somebody can share his experience as well.

---

<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:** [April 26, 2023, 9:11pm UTC](https://discuss.elastic.co/t/custom-udp-logs/328867/2 "2023-04-26T21:11:27Z")

</div>

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