# FileBeat Debug Logging not Working?

**URL:** https://discuss.elastic.co/t/filebeat-debug-logging-not-working/198012
**Category:** Beats
**Tags:** filebeat
**Created:** [September 4, 2019, 9:04am UTC](https://discuss.elastic.co/t/filebeat-debug-logging-not-working/198012 "2019-09-04T09:04:19Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![cawoodm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cawoodm/32/14083_2.png) [@cawoodm](https://discuss.elastic.co/u/cawoodm)
#### Post date: [September 4, 2019, 9:04am UTC](https://discuss.elastic.co/t/filebeat-debug-logging-not-working/198012/1 "2019-09-04T09:04:19Z")

</div>

According to the docs `filebeat -e -d "publish"` should publish debug information about each event it sends (say to LogStash). This is not the case (Windows, ELK+FB 7.3).

`filebeat.exe -c filebeat.dev.yml -e -d "publish"`

Our `filebeat.dev.yml` has `#logging.level: info` commented out.

We see the harvester starting our file and we see the event land in logstash - but filebeat does not log it - indeed no DEBUG logs appear:

```
2019-09-04T10:58:36.450+0200 INFO log/harvester.go:253 Harvester started for file: D:\tmp\log\console.dev.log
2019-09-04T10:58:42.467+0200 INFO pipeline/output.go:95 Connecting to backoff(async(tcp://ecom-repository01:5052))
2019-09-04T10:58:42.472+0200 INFO pipeline/output.go:105 Connection to backoff(async(tcp://ecom-repository01:5052)) established
2019-09-04T10:59:03.381+0200 INFO [monitoring] log/log.go:145 Non-zero metrics in the last 30s...

```

As an aside: these monitoring events are a real pain at INFO level.

---

<div class="post-metadata">

### Author: ![cawoodm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cawoodm/32/14083_2.png) [@cawoodm](https://discuss.elastic.co/u/cawoodm)
#### Post date: [September 4, 2019, 9:08am UTC](https://discuss.elastic.co/t/filebeat-debug-logging-not-working/198012/2 "2019-09-04T09:08:33Z")

</div>

`filebeat -d "*"` does show the Publish events but `filebeat -d "Publish"` (uppercase) does not. So how do these selectors work exactly?

`filebeat -d "*"`

> 2019-09-04T11:07:53.030+0200 DEBUG [processors] processing/processors.go:183 Publish event: {  
> "@timestamp": "2019-09-04T09:07:48.025Z",  
> "@metadata": {  
> "beat": "filebeat",  
> "type": "\_doc",  
> "version": "7.3.0"

---

<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: [October 2, 2019, 9:08am UTC](https://discuss.elastic.co/t/filebeat-debug-logging-not-working/198012/3 "2019-10-02T09:08:36Z")

</div>

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