Use our Vector output sink to connect your Vector-monitored log data to New Relic. Read on to learn how to configure and test the Vector New Relic logs sink.
Compatibility and requirements
To forward your logs to New Relic using Vector, ensure your configuration meets the following requirements:
- New Relic license key (recommended) or Insert API key
- Vector version 0.7.0 or higher
Configure the Vector New Relic Logs sink
To configure the Vector New Relic logs sink:
Choose one of the following options for adding a snippet to your
vector.conf
file (located in/etc/vector
by default):Restart the Vector service to ensure your changes are applied.
Test the Vector New Relic logs sink
To test if the New Relic logs sink is forwarding events:
Run the following command to append a test log message to your log file:
echo "test message" >> /PATH/TO/YOUR/LOG/FILE
Search New Relic Logs UI for your test message.
View log data
If everything is configured correctly and your data is being collected, you should see data logs in both of these places:
New Relic tools for running NRQL queries. For example, you can execute a query like this:
SELECT * FROM Log
What's next?
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.
For more help
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.