New Relic's Kubernetes plugin for log forwarding simplifies sending logs from your cluster to New Relic logs. It uses a standalone Docker image and runs as a DaemonSet, seamlessly collecting logs for centralized analysis and troubleshooting. Forwarding your Kubernetes logs to New Relic will give you enhanced l capabilities to collect, process, explore, query, and alert on your log data.
Enable Kubernetes for log management
To forward your Kubernetes logs to New Relic with our plugin:
- Install the New Relic Kubernetes integration following the steps from this page. This integration includes the Kubernetes plugin for logs.
- Optionally, you can further tune your installation in Step 3 from the guided install using the numerous configuration options available in the newrelic-logging repository. 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.
Did this doc help with your installation?
View log data
If everything is configured correctly and your data is being collected, you should see log data in both of these places:
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.
Disable log forwarding
To disable log forwarding capabilities, you can uninstall the Kubernetes plugin by following the steps outlined here. You do not need to do anything else in New Relic.