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

# Datadog

> Connect Datadog to your Atako agents — 18 read and 10 write actions.

Let your agents watch and act on your Datadog — monitors, dashboards, logs, metrics, events, incidents, hosts, SLOs and downtimes.

## Connection

* **Authentication**: API key (api\_key:app\_key).
* **Required settings**:
  * **Site** — Your Datadog site (see the URL you log in at)

<Note>
  Datadog → Organization Settings → API Keys → New Key → copy the API key. Then Organization Settings → Application Keys → New Key → copy the application key. Paste both joined by a colon: api\_key:app\_key. The application key inherits your user's permissions — for scoped keys grant at least monitors\_read, dashboards\_read, logs\_read\_data, events\_read, incident\_read, hosts\_read and slos\_read (add monitors\_write, events\_write, incident\_write, monitors\_downtime and hosts\_write for the write actions).

  See [Datadog's documentation](https://docs.datadoghq.com/account_management/api-app-keys/).
</Note>

## Read actions (18)

| Action                | Description                                                             |
| --------------------- | ----------------------------------------------------------------------- |
| `get_dashboard`       | Fetch a dashboard definition (widgets, layout) by id.                   |
| `get_downtime`        | Fetch a single downtime by id.                                          |
| `get_event`           | Fetch a single event from the event stream by id.                       |
| `get_incident`        | Fetch a single incident by id.                                          |
| `get_monitor`         | Fetch a single monitor by id, with its current state.                   |
| `get_slo`             | Fetch a single service level objective by id.                           |
| `list_active_metrics` | List metrics actively reporting since a POSIX timestamp.                |
| `list_dashboards`     | List all dashboards (title, url, author) in the organization.           |
| `list_downtimes`      | List scheduled downtimes, optionally only those currently active.       |
| `list_events`         | List events from the event stream between two POSIX timestamps.         |
| `list_hosts`          | List hosts reporting to Datadog, with filter and sort.                  |
| `list_incidents`      | List incidents, newest first, with offset pagination.                   |
| `list_monitors`       | List monitors, optionally filtered by name, tags or group states.       |
| `list_slos`           | List service level objectives, optionally filtered by query or tags.    |
| `query_metrics`       | Query timeseries metric points between two POSIX timestamps.            |
| `search_incidents`    | Search incidents with a query string (facets like state:, severity:).   |
| `search_logs`         | Search log events with a Datadog logs query over a time range.          |
| `search_monitors`     | Search monitors with a query string (facets like status:, tag:, type:). |

## Write actions (10)

| Action              | Description                                                                 |
| ------------------- | --------------------------------------------------------------------------- |
| `cancel_downtime`   | Cancel a scheduled downtime by id.                                          |
| `create_incident`   | Declare a new incident with a title and customer-impact flag.               |
| `create_monitor`    | Create a monitor from a type, query and notification message.               |
| `mute_host`         | Mute a host, optionally until a given time and with a note.                 |
| `mute_monitor`      | Mute a monitor, optionally for one scope and until a given time.            |
| `post_event`        | Post an event to the Datadog event stream.                                  |
| `schedule_downtime` | Schedule a downtime muting monitors by id or tags for a scope.              |
| `unmute_host`       | Unmute a host.                                                              |
| `unmute_monitor`    | Unmute a monitor, for one scope or all scopes.                              |
| `update_monitor`    | Update an existing monitor (name, query, message, tags, priority, options). |

## Permissions

Every action above must be explicitly granted to an agent before it can be used. See [Permissions](/integrations/permissions) for the grant model and [Security](/integrations/security) for how credentials are protected.