> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/integrations/siem/datadog.md).

# Datadog

Learn how to send events to Datadog from Couchdrop

## Introduction

Couchdrop can send selected logging events to Datadog, allowing you to include Couchdrop activity within your existing Datadog logging environment.

To configure the integration, you will connect Couchdrop to Datadog using a Datadog **Application Key** and **API Key**, select the Couchdrop events you want to send, and optionally configure additional Datadog log attributes.

## How to configure Datadog logging

{% hint style="warning" %}

#### Before you start

To connect Couchdrop to Datadog, you will need:

* Administrator access to your Couchdrop tenant
* A **Datadog Application Key**
* A **Datadog API Key**

For information on configuring Datadog API access, see the [Datadog Logs API documentation](https://docs.datadoghq.com/api/latest/logs).
{% endhint %}

{% stepper %}
{% step %}

### Open the Datadog logging provider

Log in to Couchdrop and navigate to **Admin Panel > Logging**.

Find the **Datadog** provider and select **Connect/Manage**.
{% endstep %}

{% step %}

### Select the events to send

Select the Couchdrop events that you want to send to Datadog.

Only the events selected here will be sent through the Datadog logging integration.
{% endstep %}

{% step %}

### Configure Datadog

Enter the required Datadog credentials:

* **Datadog Application Key** — Enter the Application Key for your Datadog account.
* **Datadog API Key** — Enter the API Key used to authenticate with Datadog.

You can also configure the following optional Datadog attributes:

<table><thead><tr><th>Setting</th><th width="154.390625">Datadog attribute</th><th>Description</th></tr></thead><tbody><tr><td><strong>Datadog integration name</strong></td><td><code>ddsource</code></td><td>Sets the integration or source associated with the logs.</td></tr><tr><td><strong>Datadog Tags</strong></td><td><code>ddtags</code></td><td>Adds Datadog tags to the logs sent by Couchdrop.</td></tr><tr><td><strong>Originating Hostname</strong></td><td><code>hostname</code></td><td>Sets the hostname associated with the logs.</td></tr><tr><td><strong>Service Name</strong></td><td><code>service</code></td><td>Sets the Datadog service associated with the logs.</td></tr></tbody></table>
{% endstep %}

{% step %}

### Save the integration

Click **Save Updates** to save the Datadog configuration.

Couchdrop will use the configured credentials and attributes when sending the selected events to Datadog.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.couchdrop.io/integrations/siem/datadog.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.