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

# Datadog

The Datadog driver validates the API and application keys, then performs one bounded monitor-read request.

## Required values

| Type          | Field             | Example                      |
| ------------- | ----------------- | ---------------------------- |
| Configuration | `site`            | `datadoghq.com`              |
| Configuration | `api_url`         | Optional custom API base URL |
| Secret        | `api_key`         | Datadog API key              |
| Secret        | `application_key` | Datadog application key      |

Use the Datadog site assigned to the account, such as `datadoghq.com` or the appropriate regional site.

## Provider preparation

1. Create a dedicated API key for Kangal.
2. Create a scoped application key with monitor-read permissions.
3. Record the account's Datadog site.

## Configure Kangal

1. Open **Integrations** and select **Datadog**.
2. Enter the Datadog site.
3. Enter both keys in their secret fields.
4. Save and run a sync.

## Data returned

The driver calls `/api/v1/validate` and requests the first monitor page with a page size of one. The result records key validity and monitor-read access.

## Common failures

* **401:** one or both keys are invalid.
* **403:** the application key lacks the required permission.
* **404 or DNS failure:** the configured Datadog site or custom API URL is incorrect.
* **429:** wait for the provider retry window and review the recorded rate-limit metadata.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kangal.dev/integrations/datadog.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.