New Relic's log monitoring allows you to collect, process, explore, visualize, and alert on your log data using your existing log forwarder. Read on to learn how to enable this feature and start using it.
To use log monitoring, ensure your configuration meets the following requirements:
Enable log monitoring in New Relic
There are several ways of bringing your logs into New Relic:
- Use a log forwarding plugin (like Fluentd).
- Use the New Relic Logs API.
- Use the New Relic Infrastructure agent.
Enable log monitoring in New Relic using a log forwarding solution
You can use any of these solutions to forward your logs to New Relic:
- AWS Lambda for sending logs from S3
- AWS CloudWatch plugin
- AWS Kinesis Firehose
- AWS FireLens plugin
- Fluent Bit plugin
- Fluentd plugin
- Kubernetes plugin
- Infrastructure agent
- Logstash plugin
- Vector plugin
Enable using the Logs API
If you prefer to connect to New Relic without installing a plugin, New Relic offers HTTP input integration. This will allow you to send your monitored log data directly to New Relic via the Log API.
For more information, see Introduction to Log API.
Enable log monitoring using the infrastructure agent
You can forward your logs to New Relic using the Infrastructure agent, our lightweight data collector, without having to use additional software.
For more information, see Forward your logs using the New Relic infrastructure agent.
Now that you've enabled Logs, here are some potential next steps:
- Explore your data using the Logs UI.
- Configure your agent to see contextual log data, such as distributed tracing, stack traces, application logs, and more.
- Query your data and create custom dashboards or alerts.
If no data appears after you enable New Relic Logs, follow the troubleshooting procedures.