-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Windows container FluentBit querying Windows event logs #2290
Comments
@inosvaruag This is already (partly) possible. The common solution is to map the log directory of the host machine
With this configuration, the guest can see the host log (e.g. The Event Log part is not possible as of now, and indeed a bit tricky. We can have more detailed discussion if you can share your |
@fujimotos - yes I'm aware that FluentBit can be used to fetch file logs by mounting a container. This feature request is more about adding event log support for containerized FluentBit |
I've opened an identical request on FluentD's eventlog plugin - fluent/fluent-plugin-windows-eventlog#65. It would be great to see similar support in FluentBit. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
This feature looks like a MUST for Fluentbit Windows Container to collect Windows Logs, :( |
Is your feature request related to a problem? Please describe.
FluentBit currently only runs as a service or local process. It cannot be used as a container on Windows and get the underlying VM's logs.
Describe the solution you'd like
Allow FluentBit to accept credentials and login to the underlying host for getting access to logs - event logs, files, etc. WMI Remoting, Powershell remoting, CIM sessions, etc. could be used for establishing this connection.
Describe alternatives you've considered
There is no way of running FluentBit to get underlying VM's logs.
The text was updated successfully, but these errors were encountered: