# Logstash UDP input ingest big payloads

**URL:** <https://discuss.elastic.co/t/logstash-udp-input-ingest-big-payloads/356790>\
**Category:** Logstash\
**Created:** [April 4, 2024, 2:57pm UTC](https://discuss.elastic.co/t/logstash-udp-input-ingest-big-payloads/356790 "2024-04-04T14:57:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vivere-dally](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vivere-dally/32/132789_2.png) [@vivere-dally](https://discuss.elastic.co/u/vivere-dally)\
**Post date:** [April 4, 2024, 2:57pm UTC](https://discuss.elastic.co/t/logstash-udp-input-ingest-big-payloads/356790/1 "2024-04-04T14:57:06Z")

</div>

Hi. I have a simple Logstash pipeline:

```auto
input {
	udp {
		port => 50001
		codec => "json"
	}
}

output {
	elasticsearch {
		// elastic data
	}
}

```

I observed that when I submit a bigger payload it does not get ingested. Is there any way to tackle this? I have not been able to determine the current size, but when I submit a couple of KBs I get some logs that it was not ingested.

I would like to send messages that are a couple of MB in size. Would that be feasible?

---

<div class="post-metadata">

**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\
**Post date:** [April 4, 2024, 5:09pm UTC](https://discuss.elastic.co/t/logstash-udp-input-ingest-big-payloads/356790/2 "2024-04-04T17:09:12Z")

</div>

There is [a buffer limit](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-udp.html#plugins-inputs-udp-receive_buffer_bytes).  
However, I would suggest to use the ruby debug for more details.

```auto
output {
	elasticsearch {
		// elastic data
	}
    stdout {codec => rubydebug{} }
}

```