Filebeat config check isn't reliable

With that config

fields:
  domain: XXXXXXXXX
filebeat:
  config:
    inputs:
      enabled: true
      path: /etc/filebeat/inputs.d/*.yaml
      reload:
        enabled: true
        period: 30s
    modules:
      path: /etc/filebeat/modules.d/*.yaml
      reload:
        enabled: true
        period: 30s
output:
  logstash:
    hosts:
    - XXX.XXX.fr:5XXX

The command filebeat test config answer Config OK

But when you type filebeat modules enable logstash you got :

Error in modules manager: wrong settings for config.modules.path, it is expected to end with *.yml. Got: /etc/filebeat/modules.d/*.yaml

This is not a loyal check...

Maybe the test config doesn't check that to let you be able to give another directory...
Thus you should at least give a warning : Your config is cool but be carefull you can't use modules enable command line...

Another tricks would be to change the path argument to a paths argument with a list of paths to detect modules or inputs in config object.

Thanks for your attention.

Regards,

J. Avond

I admit I don't understand the problem here. Did you create .yaml files and filebeat complain that it expects .yml ones?

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