Newrelic Fluent Bit Output

[](https://opensource.newrelic.com/oss-category/#community-plus)

Fluent Bit output plugin for New Relic

The **newrelic-fluent-bit-output** plugin forwards output to New Relic. It works on all versions of Fluent Bit greater than 0.12 but for the best experience we recommend using versions greater than 1.0. This project is provided AS-IS WITHOUT WARRANTY OR SUPPORT, although you can report issues and contribute to the project here on GitHub.

You can download the output plugin pre-compiled under our [releases](https://github.com/newrelic/newrelic-fluent-bit-output/releases/latest). Alternatively you can compile the plugin yourself and store `out_newrelic-linux-*.so` or `out_newrelic-windows-*.dll` at a location that can be accessed by the fluent-bit daemon. See to [this section](DEVELOPER.md#compiling-the-out_newrelic-plugin) in [DEVELOPER.md](DEVELOPER.md) for more details. The plugin, together with Fluent Bit, is also delivered as a standalone [Docker image](#docker-image).

Note that for certain Linux Enterprise users, [including CentOS 7, Debian 8 and 9, Ubuntu, and Raspbian 8](https://fluentbit.io/documentation/0.13/installation/td-agent-bit.html), the name of Fluent Bit is td-agent-bit, instead of fluent-bit. So, anywhere in this doc where it says `fluent-bit`, just replace it with `td-agent-bit` (for example, you will need to edit `td-agent-bit.conf` instead of `fluent-bit.conf`).

In order to insert records into New Relic, you can configure the plugin with a config file or configure it via command line flags. You can find more details on how to configure Fluent Bit [here](https://docs.fluentbit.io/manual/configuration).

Getting started with the Fluent Bit output plugin for New Relic

Fluent Bit needs to know the location of the New Relic output plugin, and the license/api key for outputting to New Relic. It is **vitally important*