The Files.com integration with Datadog enables the seamless transfer of Files.com log files to your Datadog environment via Datadog’s HTTP Logs API. This ensures that your data is current and available for real-time analysis.

You can configure the integration to send a range of log data directly to Datadog, effectively integrating Files.com as a data source for your Datadog dashboards and analytics.

Getting Started with Datadog Integration

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

Configuring Files.com for Datadog Integration

When configuring the Datadog integration in Files.com, provide a Name for the integration for your records. Then, specify Datadog's HTTP endpoint URL (typically it is http-intake.logs.us5.datadoghq.com) as the Destination URL. For authentication, generate the API key from the same Datadog instance and use it as your Datadog token in Files.com.

Datadog's HTTP endpoint URL may vary depending on the geo-region where your instance is hosted or if you are using a Datadog trial or demo account. Refer to Datadog'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 Datadog setup.

Choosing Log Types to Forward to Datadog

When setting up the Datadog integration with Files.com, you can choose which log types to send to your Datadog instances. 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 Datadog platform.

Troubleshooting

If you encounter any issues with forwarding or receiving logs in Datadog, start by verifying that your Datadog's HTTP endpoint URL and API Key are accurate and correctly configured in Files.com as the Destination URL and Datadog 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 Datadog 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 Datadog's troubleshooting documentation for further troubleshooting steps.