I have a running metricbeat service with logging configured to default destination - /var/log/metricbeat/metricbeat. The issue is that when I run some beats command like metricbeat modules list metricbeat's log file gets overwritten by the logs of recently executed command and service though still working does not log anything anymore. The problem is resolved when I restart the service but I would prefer to avoid that if possible.
Am I doing something wrong or is it a known issue with beats (the same is with filebeat) which can be workaround somehow?
But if that's the default behaviour, as you have said, then I would consider this to be a bug that in default setup and pretty standard use case the log file of a running service gets corrupted. What's more, since it's happening without any warning, the problem might pass unnoticed until much later when there is an actual need to check service logs.
Should I submit a ticket in beats issue tracker then?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.