Closed kanlas-net closed 5 years ago
My fault, I provide path to files while it needs path to folders
Hi @1Stedy,
the list_log_files
option takes a list of directories not single files. Those directories are then scanned and reported back to the Graylog server. So an admin can see what log files exist and which of them were updated recently. Just provide a list of directories instead and it should work.
@mariussturm - I actually have a use case where I do want to monitor specific log files. I note that when going into the Graylog web portal > Collector Configuration I am able to target specific files to monitor with filebeat, such as below:
filebeat.inputs:
However, if I enter this into the sidecar.yml configuration the service does not start as indicated by @1Stedy . This is problematic as I would prefer to leverage ansible for deploying the targeted log files.
@mariussturm is this something which could be reopened as an issue as I believe it would be very nice to have greater flexibility?
@on3iropolos what you are talking about is the actual Filebeat configuration, don't put this into the sidecar.yml. Please read about the basic concept and how the Sidecar is deploying the Filebeat configuration in our docs: http://docs.graylog.org/en/3.1/pages/sidecar.html
@mariussturm Thanks for the explanation. Now I understand that the graylog configuration list_log_files is not which files are logged, but which files to display on the page for the collector id.
Problem description
Sidecar can't start with logs listed in configuration
Steps to reproduce the problem
Config with line
list_log_files: "/var/log/"
works wellEnvironment