New Relic

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

You can configure the integration to send several types of log data to New Relic for monitoring and analysis.

Getting Started with New Relic Integration

Files.com uses New Relic's HTTP Logs API endpoint to send logs to a New Relic instance over HTTP or HTTPS, with License key based authentication. After you generate a License key, Files.com transmits logs to New Relic's HTTP endpoint in JSON format. No intermediate log forwarder is required.

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 varies depending on the geo-region where your instance is hosted and whether 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.

To pass extra headers to your New Relic setup, configure additional headers by specifying the Header Name and Header Value in the Key and Value fields.

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, and you can customize the log types collected for each instance. Refer to the Log Types section for the available options.

Troubleshooting

If you encounter issues forwarding or receiving logs in New Relic, first verify 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.

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

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