# Datadog

![Datadog Announces Global Strategic Partnership with AWS for Observability and Security | Datadog](https://assets.relyanceuat.xyz/images/docs/6441274388493/ext-bca4f53b9b.jpg)
Datadog is an observability service for cloud-scale applications, providing monitoring of servers, databases, tools, and services, through a SaaS-based data analytics platform. Datadog uses a Go-based agent, supports multiple cloud service providers including Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform and Red Hat OpenShift, and over 450 application integrations.

#### In Datadog:

Obtain and record the following details:

1. ***api-key***: Follow the Datadog instructions [here](https://docs.datadoghq.com/account_management/api-app-keys/#add-an-api-key-or-client-token/). In order to create an API key, the user will need the **Manage API Keys** permission.
2. ***application-key***: Follow the Datadog instructions [here](https://docs.datadoghq.com/account_management/api-app-keys/#add-application-keys/). The Application key owner must have, at minimum, the **DataDog Read Only Role**.
3. ***product***: A logical grouping to associate the integration with in the Relyance AI platform. If only one group of data will be used, you may wish to simply use your company name.
4. ***env***: The Datadog environment that Relyance AI should monitor; in the screenshot below the value will be "prod".

![5.jpg](https://assets.relyanceuat.xyz/images/docs/6441274388493/6441360287885.jpg)

### Permissions Relyance needs

Datadog authorises by key pair rather than by scope:

| Credential | Needs |
| --- | --- |
| **API key** | the **Manage API Keys** permission to create it |
| **Application key** | an owner holding at least the **Datadog Read Only Role** — the application key inherits its owner's permissions, so a key owned by an admin grants more than Relyance needs |

Relyance requests read-only access. If the application key's owner later loses
their role, the key stops working — so create it under an account that will
outlast the person who set the integration up.

#### In Relyance AI:

![Screenshot 2025-11-03 at 2.10.36 PM.png](https://assets.relyanceuat.xyz/images/docs/6441274388493/40818019615245.png)
1. Login to your Relyance AI account.
2. Navigate to the **Settings** (bottom-left corner).
3. Select **Integrations**.
4. Search and locate the **Sentry** integration card and click on it.
5. Click on the **Add Connection** button on the top right.
6. Provide a meaningful name for the integration and click on the **Add** button.
7. In the **Overview** section, select the integration features you wish to enable for the integration, review the **Scope and Permission**, and **Endpoint** details and click on **Continue**. For more details, see[Integration Features](/docs/introduction-to-relyance-ai/integration-features/).
8. In the **Connection** section, provide the appropriate values and click on **Continue**,
    - **Connection Name**: This property allows you to update the integration specified in Step 6. If you have multiple integrations for the same vendor, you may want to assign distinct names to each. This helps streamline filtering by **Discovery Source** across the **Inventory**, **Visual** **Maps**, **Assets**, and **Data Flow Analysis** pages.
    - **Rescan Frequency**: This property allows you to configure how often Relyance executes scans against this Vendor connection.
    - **Business Atlas Associations** (required): the business entities or products that newly discovered third parties, services and assets from this integration are attributed to. Choose at least one from the **Select Associations** dropdown — the wizard will not advance past this step without one. For more details, see [Business Atlas](/docs/other-settings/business-atlas-overview/).
9. In the **Authentication** section, provide the details captured from the **Datadog** application and click on **Authenticate**.
10. This step applies only if the **Data Inspection** check box was enabled in Step 7. In the Data Inspection section, provide the appropriate values and click on **Continue**,
    - **Minimum Confidence Level:** This property adjusts the sensitivity of the Data Inspection feature. Lower likelihoods (e.g., unlikely) offer more coverage but may produce false positives, while higher sensitivity (e.g., very likely) provides greater accuracy but less coverage.
11. Review the configuration summary from the **Completion** section and click on **Finish.**
12. Confirm the integration Status reflects **Connected.**

![Screenshot 2025-11-03 at 2.11.36 PM.png](https://assets.relyanceuat.xyz/images/docs/6441274388493/40818046457741.png)

![Screenshot 2025-11-03 at 2.12.52 PM.png](https://assets.relyanceuat.xyz/images/docs/6441274388493/40818019616397.png)

![Screenshot 2025-11-03 at 2.14.41 PM.png](https://assets.relyanceuat.xyz/images/docs/6441274388493/40818046458381.png)

![Screenshot 2025-11-03 at 2.15.23 PM.png](https://assets.relyanceuat.xyz/images/docs/6441274388493/40818046458893.png)

![A connection's detail view: scopes, endpoints and per-resource scan status](https://assets.relyanceuat.xyz/images/docs/ui/datadog/08-connection-detail.png)

<!-- auth-methods:begin (generated from the integration catalog; do not hand-edit) -->

## Authentication methods and fields

Pick one of these under **Authentication Method** on the connection wizard's **Authentication** step. This table is generated from the integration catalog, so it always matches what the form actually asks for.

| Method | Required | Optional |
| --- | --- | --- |
| **Custom** | `Account Details` | — |

<!-- auth-methods:end -->

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). Non-secret fields go in `auth.params`; secret fields go in `auth.secrets_wo`, which is write-only — never stored in Terraform state. Rotate secrets by bumping `auth.secrets_wo_version`.

```hcl
resource "relyance_integration_connection" "datadog" {
  vendor = "datadog"
  name   = "<your connection name>"

  auth = {
    method = "account-credentials"
    params = {
      accounts = jsonencode([
        {
          api-key = ""
          application-key = ""
          datadog-url = "https://api.datadoghq.com/"
          env = ""
          product = ""
        }
      ])
      data_storage_location = "us"
    }
  }

  scans = { "data-inspection" = { enabled = true } }
}
```

<!-- terraform-examples:end -->