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

# Datadog integration

Connect your Datadog organization to Seal to see Seal's package metrics and events in Datadog.

The Datadog integration sends what Seal knows about your projects into your own Datadog organization. Each hour it sends counts of vulnerable and sealed packages. It also sends an event each time Seal releases a sealed version for a package you use and each time Seal starts tracking a new project. You can chart this data, alert on it and correlate it with the rest of your Datadog data.

{% hint style="info" %}
The Datadog integration is opt-in and enabled per tenant. To turn it on for your tenant, contact your Seal account team. Until it is enabled, the Datadog card does not appear under **Settings > Integrations**.
{% endhint %}

## Connecting Datadog

A Seal tenant connects to exactly one Datadog organization. You always start the connection from the Seal Security tile in Datadog:

1. Under **Settings > Integrations** in the Seal UI, click the **Datadog** card (**Click to connect**). This opens the Seal Security tile in Datadog. You can also find the tile on Datadog's Integrations page.
2. On the tile, click **Connect Accounts**. Datadog sends you to the Seal UI, which then sends you back to Datadog to authorize Seal.
3. Approve the authorization in Datadog. Seal asks Datadog to create an API key in your organization and uses that key to submit data.
4. The Seal UI shows **You are now connected to Datadog!** and returns you to **Settings > Integrations**, where the Datadog card now shows **Connected**.

Seal sends the first snapshot of package counts as soon as the connection completes, so the dashboard has data right away.

Seal supports these Datadog sites: `datadoghq.com` (US1), `us3.datadoghq.com`, `us5.datadoghq.com`, `datadoghq.eu`, `ap1.datadoghq.com`, `ap2.datadoghq.com` and `uk1.datadoghq.com`.

### If the connection fails

* **"Datadog did not create an API key."** Datadog keeps one Seal Security API key per organization. If the organization was connected before, delete its Seal Security API key on Datadog's **API Keys** page and connect again.
* **"Datadog connection cancelled."** You declined the authorization in Datadog. Start again from the tile.
* **"Start the connection again from the Seal Security tile in Datadog."** The redirect from Datadog was incomplete. Start again from the tile.

## Data Seal sends to Datadog

### Metrics

Seal sends these gauges every hour. They match the numbers on the Seal dashboard page, which refresh once a day.

| Metric                              | Tags       | Description                                                         |
| ----------------------------------- | ---------- | ------------------------------------------------------------------- |
| `seal_security.packages.vulnerable` | `severity` | Number of vulnerable packages pulled by your projects, by severity. |
| `seal_security.packages.sealed`     | `severity` | Number of sealed packages pulled by your projects, by severity.     |
| `seal_security.fixes.available`     | none       | Number of vulnerable packages that have a sealed version available. |

`severity` is one of `critical`, `high`, `medium` or `low`.

### Events

All events carry the source `seal-security`.

* **Sealed version released for `<package>`.** Seal released a sealed version for a package your projects use. The event lists the vulnerabilities it fixes and is tagged `library_name`, `sealed_version` and `severity` (the highest severity among the fixed vulnerabilities).
* **Seal is now tracking `<project>`.** Seal started tracking a new project. Tagged `project_name`.

### Dashboard and monitor

The Seal Security tile includes:

* The **Seal Security Overview** dashboard: your current exposure from the latest snapshot, the sealed versions Seal released, and the projects Seal tracks. Filter it with the `severity` template variable.
* A recommended monitor, **The number of critical vulnerable packages increased in the libraries your projects use**, which alerts when your projects pull more critical vulnerable packages than a day earlier.

## Viewing and disconnecting the connection

Click the **Datadog** card under **Settings > Integrations** to open its drawer, which shows the Datadog site the tenant is connected to. To disconnect, click the delete icon in the drawer and confirm.

After you disconnect, Seal stops sending data and deletes its copy of the credentials. Datadog does not let Seal delete the API key it created, so delete the Seal Security API key on Datadog's **API Keys** page yourself. You must delete it before you connect the organization again.

If Datadog reports that the Seal Security API key is no longer valid (for example, after you delete it in Datadog), Seal disconnects the integration automatically.

## Related

* [Managing source-control connections](https://docs.sealsecurity.io/discovering/connecting-source-control/managing-connections.md): the **Settings > Integrations** page.
* [The Notification Center](https://docs.sealsecurity.io/using-platform/notification-center.md): the other channels for the new sealed version notification.
