> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/enterprise-guide/jp/event-reporting/datadog.md).

# Datadog

Keeper SIEMからDatadogへのプッシュ連携

### 概要

KeeperはDatadogへのイベントストリーミングに対応しています。外部へのログ出力はリアルタイムで行われ、新しいイベントは数分以内に表示されます。設定手順は以下のとおりです。

<figure><img src="https://3468650114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeJwa6ByNJ2qindnPknCW%2Fuploads%2FzExVLng0QORK3t9n0doL%2FJP_Datadog.png?alt=media&amp;token=19683477-3a8c-4684-bfd2-ee8941b77235" alt=""><figcaption></figcaption></figure>

Datadog連携では、以下の2つのフィールドが必要です。

* URL
  * **datadoghq.com** (US1, Ashburn)
  * **datadoghq.eu** (EU1, Frankfurt)
  * **us3.datadoghq.com** (US3, GCP)
  * **us5.datadoghq.com** (US5, AWS US-West-2)
  * **ap1.datadoghq.com** (AP1, Tokyo)
  * **ddog-gov.com** (US1-FED, GovCloud)
  * **ap2.datadoghq.com** (AP2, Australia)
* APIキー

APIキーは、以下の手順で取得します。

* Datadogの画面で **\[組織設定]** > **\[APIキー]** に進みます。
* 新しいAPIキーを作成します。

APIキーは、Datadog環境の送信先サーバーと一致させてください。


---

# 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.keeper.io/enterprise-guide/jp/event-reporting/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.