Overview
Right now, Fluent Bit is designed to run on Unix platforms (Linux, BSD and OSX).
This ticket aims to expand the supported platforms a bit more; Namely we want
to be able to run Fluent Bit on Windows, and make it possible to ship logs
efficiently from there.
Goals
- Make the core engine of Fluent Bit runnable on Windows.
- Our primary build target is MSVC 2017.
- (Cygwin and MinGW are out of our scope for now)
- Create an installation package so that users can install easily
- Maybe
setup.exe or fluent-bit.msi; We need to figure out how to do it.
- Migrate plugins as many as possible (see below)
Roadmap
ETA of this feature (Windows support) is 2019 1Q.
We don't expect all plugins being migrated to Windows by the end of March 2019,
though. The high priority list of plugins is attached to this ticket.
Also we are planning to create a new input plugin for Windows event logs
(maybe in_windows_eventlog). This plugin should be included in the initial
release of Windows support.
List of plugins to be ported
- Input Plugins
- Filter Plugins
- filter_grep
- filter_lua
- filter_modify
- filter_record_modifier
- filter_stdout
- Output Plugins
- out_es
- out_kafka
- out_flowcounter
- out_counter
- out_http
- out_splunk
Overview
Right now, Fluent Bit is designed to run on Unix platforms (Linux, BSD and OSX).
This ticket aims to expand the supported platforms a bit more; Namely we want
to be able to run Fluent Bit on Windows, and make it possible to ship logs
efficiently from there.
Goals
setup.exeorfluent-bit.msi; We need to figure out how to do it.Roadmap
ETA of this feature (Windows support) is 2019 1Q.
We don't expect all plugins being migrated to Windows by the end of March 2019,
though. The high priority list of plugins is attached to this ticket.
Also we are planning to create a new input plugin for Windows event logs
(maybe
in_windows_eventlog). This plugin should be included in the initialrelease of Windows support.
List of plugins to be ported