Datadog

The Files.com integration with Datadog transfers Files.com log files to your Datadog environment through Datadog's HTTP Logs API, keeping your data current and available for real-time analysis.

You can configure the integration to send a range of log data directly to Datadog, making Files.com 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 over HTTP or HTTPS, with API Key based authentication. Generate an API Key in your Datadog instance and configure Files.com to transmit logs to Datadog's HTTP endpoint in JSON format. No intermediate log forwarder is required.

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 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 varies 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 for the correct HTTP endpoint URL for your environment.

If you need to pass extra headers to your Datadog setup, configure them by specifying the Header Name and Header Value in the Key and Value fields.

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. All log types are enabled by default, and you can customize the log types collected for different instances. Refer to the Log Types section for the available options for forwarding logs to your Datadog platform.

Troubleshooting

If you run into issues with forwarding or receiving logs in Datadog, start by verifying that your Datadog HTTP endpoint URL and API Key are accurate and correctly configured in Files.com as the Destination URL and Datadog token.

If the problem continues, check for network connectivity issues or firewall rules that may be blocking communication between Files.com and your Datadog 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 persists, refer to Datadog's troubleshooting documentation for further steps.