If your log data is already being monitored by Fluent Bit, you can use our Fluent Bit output plugin to forward and enrich your log data in New Relic. This plugin is also provided in a standalone Docker image that can be installed in a Kubernetes cluster in the form of a DaemonSet. We refer to this as our Kubernetes plugin.
Forwarding your Kubernetes logs to New Relic will give you enhanced log management capabilities to collect, process, explore, query, and alert on your log data.
To forward your logs to New Relic with our Kubernetes plugin for Fluent Bit:
- Make sure you have:
- Follow the procedures in GitHub to install the Kubernetes plugin.
- Optional: If you are installing the plugin as a Helm chart, you can set numerous configurations. However, we recommend the standard setup, as it is valid for most users.
- Generate some traffic and wait a few minutes, then check your account for data.
If everything is configured correctly and your data is being collected, you should see data logs in both of these places:
- New Relic's Logs UI
- New Relic tools for running NRQL queries. For example, you can execute a query like this:
SELECT * FROM Log
If no data appears after you enable our log management capabilities, follow our standard log troubleshooting procedures.
Explore logging data across your platform with our Logs UI.
- Get deeper visibility into both your application and your platform performance data by forwarding your logs with our logs in context capabilities.
- Set up alerts.
- Query your data and create dashboards.
To disable log forwarding capabilities, follow standard procedures in Kubernetes documentation. You do not need to do anything else in New Relic.