On linux, the runtime doesn't change path.data & path.logs based on the config settings in the filebeat configuration.
You need different path.data & path.logs directories for the runtime to work when using the tags system, but seems like path.data & path.logs are "hardcoded" some where and therefor doesn't get the directory listed in filebeat's config.
Steps to reproduce the problem
default config for filebeat:
the systemd service starts filebeat with:
/usr/share/filebeat/bin/filebeat --path.home /usr/share/filebeat --path.config /etc/filebeat --path.data /var/lib/filebeat --path.logs /var/log/filebeat -c /var/lib/graylog-sidecar/generated/648a0c4345c6352ac3bc9698/filebeat.conf
Problem description
On linux, the runtime doesn't change
path.data
&path.logs
based on the config settings in the filebeat configuration. You need different path.data & path.logs directories for the runtime to work when using the tags system, but seems likepath.data
&path.logs
are "hardcoded" some where and therefor doesn't get the directory listed in filebeat's config.Steps to reproduce the problem
default config for filebeat:![Screenshot 2023-08-01 at 2 12 20 PM](https://github.com/Graylog2/collector-sidecar/assets/1403731/a4a4ed89-ceae-400b-8e3a-090fed0bd152)
the systemd service starts filebeat with:
/usr/share/filebeat/bin/filebeat --path.home /usr/share/filebeat --path.config /etc/filebeat --path.data /var/lib/filebeat --path.logs /var/log/filebeat -c /var/lib/graylog-sidecar/generated/648a0c4345c6352ac3bc9698/filebeat.conf
Environment