# Logstash is disaster

**URL:** <https://discuss.elastic.co/t/logstash-is-disaster/317151>\
**Category:** Logstash\
**Created:** [October 20, 2022, 8:23pm UTC](https://discuss.elastic.co/t/logstash-is-disaster/317151 "2022-10-20T20:23:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nikolas1306](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nikolas1306/32/111507_2.png) [@Nikolas1306](https://discuss.elastic.co/u/Nikolas1306)\
**Post date:** [October 20, 2022, 8:23pm UTC](https://discuss.elastic.co/t/logstash-is-disaster/317151/1 "2022-10-20T20:23:04Z")

</div>

200% of cpu without pipelines and not produce log

Who develops it is aware of its total unreliability?

![image](https://us1.discourse-cdn.com/elastic/original/3X/b/c/bc8b11214dc041153965659c0ee53b6157199b5d.png)

response:

deny that Logstash has problems is not the solution in my opinion and better not to use it and try to use only filebeat directly with elastic

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 20, 2022, 8:49pm UTC](https://discuss.elastic.co/t/logstash-is-disaster/317151/2 "2022-10-20T20:49:33Z")

</div>

Approaching your issue by abusing the product and its developers isn't going to;

1. encourage anyone to provide assistance to you
2. make you any friends

Please try again, be polite and remember our [code of conduct](https://www.elastic.co/community/codeofconduct).

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 20, 2022, 8:49pm UTC](https://discuss.elastic.co/t/logstash-is-disaster/317151/3 "2022-10-20T20:49:35Z")

</div>