Having an empty monitoring section in filebeat.yml generates startup errors for filebeat 7.x

[tullis]

Thanks for your work on this module.

I created a filebeat using a basic logstash output with a single host.
My generated /etc/filebeat/filebeat.yml is included below:

When puppet tries to start the service there is an error logged:

Exiting: No monitoring reporter configured

If I remove the following line from the configuration, it starts up successfully:

monitoring: {}

I am not using xpack monitoring, so I thought that the defaults should work.
I can see that the monitoring options were recently added in this commit: 5aa008e

### Filebeat configuration managed by Puppet ###
---
shutdown_timeout: '0'
name: myfqdn.example.com
tags: []
fields: {}
fields_under_root: false
filebeat:
  config.inputs:
    enabled: true
    path: "/etc/filebeat/conf.d/*.yml"
  config.modules:
    enabled: false
    path: "/etc/filebeat/modules.d/*.yml"
  shutdown_timeout: '0'
  modules: []
http: {}
output:
  logstash:
    hosts:
    - logstash_host:5044
shipper: {}
logging: {}
runoptions: {}
processors: []
monitoring: {}
setup: {}

[tullis]

I should add that I have tried filebeat 7.7 and 7.6 and they are both the same.

[pcfens]

Can you verify that the change I made works for you? I run my production cluster against this repo directly, but we're stuck on Filebeat 6.x (hopefully upgrading soon).

[tullis]

Hi @pcfens - Yes, the fix woks for me. Many thanks for the rapid response. 👍

[pcfens]

Thanks for the quick test. I just pushed it to the forge as 4.4.2.