While the typical norm is for applications to write their logs to file or to stdout (console), this isn’t the most efficient way to handle logs (particularly given I/O performance for the storage devices). Many logging frameworks have addressed this by providing more direct outputs to commonly used services such as ElasticSearch and OpenSearch. This is fine, but the only downside is that there is no means for an intermediary layer to preprocess, filter, and route (potentially to multiple services). These constraints can be overcome by using an intermediary service such as Fluent Bit or Fluentd.

Many logging frameworks can work with Fluentd by supporting the HTTP or Forward protocols Fluentd supports out of the box. But as both Fluent Bit and Fluentd are interchangeable with these protocols and logging framework that supports Fluentd, by implication also supports Fluent Bit, not to mention Fluent Bit supports OpenTelemetry.

The following table identifies a range of frameworks that can support communicating directly with Fluent Bit. It is not exhaustive but does provide broad coverage. We’ll update the table as we discover new frameworks that can communicate directly.

Language	Framework / Library	Protocol(s)	Commentary
Java	Log4J2	HTTP Appender	Send JSON payloads over HTTP (use HTTP input plugin)
Java	fluent-logger-java	Forward
Python	core language	HTTP Handler	Provides the means to send logs over HTTP – means Fluent Bit input handler can manage
Python	fluent-logger-python	Forward
Python	Fluent Logger	Forward
Node.js	fluent-logger-node	Forward
Node.js	Winston	HTTP
Go (Golang)	fluent-logger-golang	Foward
.Net (C# VB.Net etc)	NLog (NLog.Targets.Fluentd)
Ruby	fluent-logger-ruby	Forward
PHP	fluent-logger-php	Forward
Perl	fluent-logger-perl	Forward
Scala	fluent-logger-scala	Forward
Erlang	fluent-logger-erlang	Forward
OCAML	fluent-logger-ocaml	Forward