I'm trying to figure out how to configure a pipeline in my nginx filebeat module.
This link https://www.elastic.co/guide/en/beats/filebeat/master/configuring-ingest-node.html shows a general top-level configuration for all filebeats. This however is not ideal for me since it shows pre-processing errors for all other logs that fail the grok.
I have scoured the docs finding this https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-input-log.html which I used to add an entry to my nginx.yml module configuration as so
- module: nginx
# Access logs
access:
enabled: true
# Set custom paths for the log files. If left empty,
# Filebeat will choose the paths depending on your OS.
#var.paths:
pipeline: filebeat-6.4.3-nginx-access-custom
# Error logs
error:
enabled: true
# Set custom paths for the log files. If left empty,
# Filebeat will choose the paths depending on your OS.
#var.paths:
I restarted filebeat but this still doesn't take effect. I know my pipeline is correct because I have tested with the _simulate endpoint and have even overridden the default nginx pipeline and it worked as expected.