Agent fails to open files due to file locking on Windows

[nvass]

When trying to send files as logs to Datadog, it seems that the Datadog agent does not open them because they are already opened by another process. This will always be the case for log files. I've had this problem with Elasticsearch on Windows but I suspect it will be quite common with other servers running on Windows OSes.

From agent.log:
2022-03-29 11:50:20 EEST | CORE | INFO | (pkg/logs/scheduler/scheduler.go:66 in Schedule) | Received a new logs config: custom_logs
2022-03-29 11:50:20 EEST | CORE | WARN | (pkg/logs/input/file/scanner.go:205 in launchTailers) | Could not collect files: file C:\elasticsearch-7.17.1-windows-x86_64.d\elasticsearch-7.17.1-windows-x86_64\elasticsearch-7.17.1\logs\elasticsearch.log does not exist
2022-03-29 11:50:20 EEST | CORE | WARN | (pkg/logs/input/file/scanner.go:205 in launchTailers) | Could not collect files: file C:\elasticsearch-7.17.1-windows-x86_64.d\elasticsearch-7.17.1-windows-x86_64\elasticsearch-7.17.1\logs\elasticsearch_server.json does not exist

Describe what happened:
Log files cannot be opened

Describe what you expected:
Logs files should be opened and sent to Datadog as logs.

Steps to reproduce the issue:
Use Elasticsearch and try to monitor the logs directory. It should be reproducible with other servers that write log files.

Additional environment details (Operating System, Cloud provider, etc):
Microsoft Windows server 2019 Standard

[nvass]

Being unknowledgeable with regard to using Windows, it was a file permissions error.

[shtyler]

Hi @nvass, can you please describe how you solved the issue?