New Relic's log management 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.
If you don't have one already, create a New Relic account. It's free, forever.
To use log management, ensure your configuration meets the following requirements:
- Your New Relic account's license key
- A compatible log forwarding plugin installed
- Ensure outbound connectivity on TCP port 443 is allowed to the CIDR range that matches your region
The preferred configuration method is to use the DNS name
There are several ways of bringing your logs into New Relic:
- Use the New Relic infrastructure agent
- Use log forwarding plugins (like Fluentd)
- Use the New Relic Logs API
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 infrastructure agent.
You can use any of these solutions to forward your logs to New Relic:
- Infrastructure agent
- Kubernetes plugin
- AWS Lambda for sending logs from S3
- AWS CloudWatch plugin
- AWS Kinesis Firehose
- AWS FireLens plugin
- Fluent Bit plugin
- Fluentd plugin
- Logstash plugin
- Vector plugin
- Heroku Log Streaming
- Syslog TCP Endpoint
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.
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.