Filebeat 8.16.1 is not writing the filebeat logs in the specified log location.

[guru00]

Hello Team,
I recently upgraded our Filebeat agent from version 8.15.1 to 8.16.1. After the upgrade, Filebeat is running, but it is not writing any log files to the configured log location. Could you please assist me with this issue? Is this a known bug, or is there something I need to change in the filebeat.yml configuration to ensure that logs are written to the specified location in the newer version?

For confirmed bugs, please report:

• Version: 8.16.1
• Operating System: RHEL9

Please find the logging config which I have used our filebeat configuration yml file.
`# ================================== Logging ===================================
logging.level: info
logging.to_files: true
logging.json: true
logging.ecs: true
logging.metrics.enabled: true
logging.metrics:

• stats
• dataset
  logging.files:
  path: /var/log/filebeat
  keepfiles: 7
  permissions: 0644
  rotateonstartup: false`

[botelastic]

This issue doesn't have a Team:<team> label.

[guru00]

Hello Team,
Does anyone have any idea on this issue?

Thanks
Siva

[guru00]

Hello Team,
I found out the problem. I could see the similar issue request. The issue is in the latest version of Filebeat, especially after version 8.15.3; the Filebeat is not writing a log message into a file until we configure the parameter below. After configuring the parameter below, I could see my Filebeat 8.16.1 is writing logs into a file under the configured log directory.

logging.to_stderr: false

https://discuss.elastic.co/t/8-16-1-ignores-to-syslog-false/371276/3
#41767