I've actually switched over to nxlog for windows and it worked without issues, so I removed fluentbit from my powershell script and replaced it with nxlog, configured it for what I wanted to forward, put the IP addr in for the collector, and the silent install runs, you place the config where the binary is and that gets ingested and the service gets installed and started. So while not an answer for fluentbit which is used everywhere, and works well, it could have been machine specific, however I had this error on different machines. nxlog was the path of least resistance so to speak.
Microsoft recommended syslog agent for Windows Server 2019
Allen McCulloch
1
Reputation point
Hello,
I was looking to see if anyone has installed under Windows Server 2019 anything other than rsyslog agent or tds fluent-bit for forwarding logs out? Both products are still heavily slanted towards linux, tds-fluent-bit does support Windows Services however I've got it fully scripted in powershell and it shows up when I do the Get-Service fluent-bit shows stopped, but when I try to start it, it will not start and gives me the following error.
Going on fluent-bits site, and through their issue list this was fixed supposedly back in the 1.6 days. So with all this, I'm looking to see what Microsoft or others use for a syslog agent that runs as a service, or a Microsoft Product, that just works, can be installed right on the server itself, easily scripted.
Thanks,
``PS C:\td-agent-bit\td-agent-bit-1.8.11-win64\conf> Start-Service fluent-bit
Start-Service: Failed to start service 'fluent-bit (fluent-bit)'.