# Filebeat not sending to Logstash until it's terminated

**URL:** https://discuss.elastic.co/t/filebeat-not-sending-to-logstash-until-its-terminated/303565
**Category:** Beats
**Tags:** docker, windows, filebeat
**Created:** [April 29, 2022, 1:28am UTC](https://discuss.elastic.co/t/filebeat-not-sending-to-logstash-until-its-terminated/303565 "2022-04-29T01:28:26Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [April 29, 2022, 5:07pm UTC](https://discuss.elastic.co/t/filebeat-not-sending-to-logstash-until-its-terminated/303565/5 "2022-04-29T17:07:44Z")

</div>

Yes My Suggestion was to try straight from Filebeat to Elasticsearch just to test the line processing.

Also could you try just the `codec => rubydebug` instead of the json codec.

Also you could test the filebeat console output as well

> **[Configure the Console output | Filebeat Reference \[8.1\] | Elastic](https://www.elastic.co/guide/en/beats/filebeat/current/console-output.html)**

```auto
output.console:
  pretty: true

```

Yeah there is something "Unusual" going on this should all be pretty straightforward.

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-not-sending-to-logstash-until-its-terminated/303565)._
