The Files.com integration with New Relic uses New Relic's Log API to directly transmit log data to New Relic's Log Management system via New Relic's HTTP endpoint. This setup ensures that your log data is continuously updated and available for real-time analysis.

You can configure the integration to send various types of log data to New Relic, thus enhancing your monitoring, analytical capabilities, and responsiveness with greater accuracy and efficiency.

Getting Started with New Relic Integration

Files.com uses New Relic's HTTP Logs API endpoint to send logs to a New Relic instance via HTTP or HTTPS protocols, utilizing License key based authentication. By generating a License key, you can configure Files.com to transmit logs to New Relic's HTTP endpoint in the JSON format, eliminating the need for an intermediate log forwarder.

Configuring Files.com for New Relic Integration

When configuring the New Relic integration in Files.com, provide a Name for the integration for your records. Then, specify New Relic's HTTP endpoint URL (typically https://log-api.newrelic.com/log/v1 for a US-based endpoint or https://log-api.eu.newrelic.com/log/v1 for an EU-based endpoint) as the Destination URL. For authentication, generate the License key (API key) from the same New Relic instance and use that key as your New Relic token.

New Relic's HTTP endpoint URL may vary depending on the geo-region where your instance is hosted or if you are using a custom, trial or demo account. Refer to New Relic's documentation to obtain the correct HTTP endpoint URL for your environment.

You can configure additional headers by specifying the Header Name and Header Value in the Key and Value fields, respectively, if you need to pass extra headers to your New Relic setup.

Choosing Log Types to Forward to New Relic

You can configure the New Relic integration in Files.com to select which log types are forwarded to your New Relic instance. By default, all log types are enabled, but you can customize the log types collected for different instances as needed. Refer to the Log Types section to review the available options for forwarding logs to your New Relic platform.

Troubleshooting

If you encounter any issues with forwarding or receiving logs in New Relic, start by verifying that your New Relic HTTP endpoint URL and License key are accurate and correctly configured in Files.com as the Destination URL and New Relic token, respectively.

If you are still experiencing issues, check for network connectivity issues or firewall rules that may be blocking the communication between Files.com and your New Relic environment. For additional insights, review any SIEM-related logs under External Logs by selecting "SIEM" as the Event Type. These logs may help identify any issues with the log forwarding process.

If the problem persists, refer to New Relic's troubleshooting documentation for further troubleshooting steps.