# Cloud foundry wihh Logstash

**URL:** <https://discuss.elastic.co/t/cloud-foundry-wihh-logstash/125049>\
**Category:** Logstash\
**Created:** [March 21, 2018, 5:37pm UTC](https://discuss.elastic.co/t/cloud-foundry-wihh-logstash/125049 "2018-03-21T17:37:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bhushanrade](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhushanrade/32/29370_2.png) [@bhushanrade](https://discuss.elastic.co/u/bhushanrade)\
**Post date:** [March 21, 2018, 5:37pm UTC](https://discuss.elastic.co/t/cloud-foundry-wihh-logstash/125049/1 "2018-03-21T17:37:04Z")

</div>

in logstash for cloud foundry i used tcp and udp input plugin as below  
input {  
tcp {  
port =\> 5000  
type =\> syslog  
}  
udp {  
port =\> 5000  
type =\> syslog  
}  
}  
but i'm looking data resilient(persistent queue) feature of lostash.

as per logstash document tcp and upd etc don't not have a mechanism to acknowledge receipt to the sender so can not be protected from data loss(not able to use persistent queue feature). and in cloud foundry i used tcp and udp for input  
what is solution if i want to use persistent queue or any way to protect from data loss in above case ?

---

<div class="post-metadata">

**Author:** ![yaauie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yaauie/32/23363_2.png) [@yaauie](https://discuss.elastic.co/u/yaauie)\
**Post date:** [March 22, 2018, 7:31am UTC](https://discuss.elastic.co/t/cloud-foundry-wihh-logstash/125049/2 "2018-03-22T07:31:44Z")

</div>

Back-pressure is an integral part of the Beats (formerly "lumberjack") protocol, so if it's possible to install Filebeat or another appropriate Beat on your edge nodes, that's probably going to be your best bet.

The http input also supports back-pressure simply because it is customary for an http client sending data to wait for a response.

However, it is all about trade-offs. In the above scenarios, back-pressure means that when Logstash is overburdened, data will spool up on your edge nodes; if those are volatile or ephemeral, the data that has not yet shipped from them when they disappear would be lost.

---

<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 19, 2018, 7:31am UTC](https://discuss.elastic.co/t/cloud-foundry-wihh-logstash/125049/3 "2018-04-19T07:31:54Z")

</div>

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