> ## Documentation Index
> Fetch the complete documentation index at: https://docs.guild.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Datadog

> Give agents access to Datadog monitoring, metrics, and logs.

The `@guildai-services/guildai~datadog` package gives your agents access to Datadog monitoring, metrics, and log data through Guild's Datadog integration.

## Authentication

* **Type:** API key

Datadog requires two keys: an **API Key** and an **Application Key**. Guild sends them as the `DD-API-KEY` and `DD-APPLICATION-KEY` headers.

### Setup

<Steps>
  <Step title="Open Credentials">Go to **Credentials** in Guild.</Step>
  <Step title="Connect Datadog">Click **Datadog** and enter your Datadog API key, application key, and the `site` that matches your Datadog account.</Step>
</Steps>

### Site configuration

The `site` parameter tells Guild which Datadog regional endpoint to send requests to. Take it from the URL you log in at.

The standard Datadog sites are:

* `datadoghq.com` (US1)
* `us3.datadoghq.com`
* `us5.datadoghq.com`
* `datadoghq.eu` (EU1)
* `ap1.datadoghq.com`
* `ap2.datadoghq.com`
* `uk1.datadoghq.com`
* `ddog-gov.com`
* `us2.ddog-gov.com`

Guild accepts any host under `datadoghq.com`, `datadoghq.eu`, or `ddog-gov.com`, so a custom Datadog site works alongside the standard ones. A value outside those three domains is rejected with `Invalid Datadog site`.

<Note>
  `site` is exempt from the DNS-label rule Guild applies to other integration configuration parameters, which would reject a dotted hostname. See [Configuration parameter validation](/integrations/overview#configuration-parameter-validation).
</Note>

## Usage

```typescript theme={null}
import { DatadogTools } from "@guildai-services/guildai~datadog"
import { llmAgent } from "@guildai/agents-sdk"

export default llmAgent({
  description: "An agent that monitors Datadog metrics and alerts",
  tools: { ...DatadogTools },
})
```