# Help debugging ingestion flow Filebeat + Logstas

**URL:** https://discuss.elastic.co/t/help-debugging-ingestion-flow-filebeat-logstas/245277
**Category:** Logstash
**Created:** [August 17, 2020, 4:23pm UTC](https://discuss.elastic.co/t/help-debugging-ingestion-flow-filebeat-logstas/245277 "2020-08-17T16:23:27Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Xavier\_Krantz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xavier_krantz/32/59812_2.png) [@Xavier\_Krantz](https://discuss.elastic.co/u/Xavier_Krantz)
#### Post date: [August 17, 2020, 4:23pm UTC](https://discuss.elastic.co/t/help-debugging-ingestion-flow-filebeat-logstas/245277/1 "2020-08-17T16:23:27Z")

</div>

Hi everybody,

I have setup an BLEK (Beats, Logstash, ElasticSearch, Kibana) stack 😛

- ES and Kibana are running in ES Cloud
- a "cluster" of Logstash instances are running on a Kubernetes cluster
- A service and Filebeat are running from an other kubernetes cluster.

The `logstash` has been deployed from Helm & `Filebeat` while using the AllInOne file provided by the "getting Started" page of ES doc.

At some point I have a hole in my log collection for one of my service:

 ![Screenshot_20200817_171014_logs_public-api](https://us1.discourse-cdn.com/elastic/original/3X/c/5/c552b1378f54a844b59be0faa96afc37ab0d56e1.png)

The local `Filebeat` does not seems to complain. But all I get is `filebeat` saying it has metrics

 ![Screenshot_20200817_171140_logs_filebeat](https://us1.discourse-cdn.com/elastic/original/3X/a/d/ade859b663df10af248a22497a582f65225a93ff.png)

The aggregator layer with `Logstash` does not say much more during the same time window:

![Screenshot_20200817_171121_logs_logstash](https://us1.discourse-cdn.com/elastic/original/3X/e/9/e970a2624010daeac92ae04347bc015549a7bc7b.png)

The events after `00:00` seems related to an other issue that has nothing to do with this one (Complaining not beeing able to write in the index `logs-xxxx-2020-08-15` which has been moved to other nodes by the LifeCyclePolicy whereas we are 2020-08-17 ...)

But the shipped-in collectionof GCP shows logs ....

 ![Screenshot_20200817_171205_logs_public-api_gcp](https://us1.discourse-cdn.com/elastic/original/3X/2/6/267b06738320e5531b37e197e9a382f8d96354f8.png)

Does some one have a hint or an idea where I can start looking at ?

About the config of `Logstash`:

```auto
input: beats
output: elasticsearch

```

By looking at Kubernetes, neither `Filebeat` or `logstash` pods have restarted for months ...

This gives me serious doubts about the reliability of the BLEK stack ☹

---

<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: [September 14, 2020, 4:23pm UTC](https://discuss.elastic.co/t/help-debugging-ingestion-flow-filebeat-logstas/245277/2 "2020-09-14T16:23:32Z")

</div>

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