# Datadog > Connect Datadog to Tidal Control so compliance tests read your security configuration, users and monitoring setup. Read-only access to your organisation. Source: https://tidalcontrol.com/docs/integrations/datadog Tidal Control's Datadog integration monitors your organisation's security configuration, users, and monitoring setup for compliance purposes. ## What this integration monitors - **Users:** MFA status and account configuration - **Organisation settings:** SAML configuration and authentication settings - **API keys:** Usage and staleness - **Application keys:** Scope configuration - **Monitors:** Priority settings and active downtimes - **Security monitoring rules:** Whether detection rules are enabled - **CSM findings:** Cloud Security Management failed findings - **Synthetics tests:** Test status and location configuration ## Requirements - Super User role in Tidal Control - Datadog account with access to Organisation Settings ## Configuration step-by-step plan We'll create a **Datadog API key** and **application key**, then add the connection in Tidal Control. If your organisation uses a Datadog site other than the default US region, you'll also configure the site field. **Configuration steps:** 1. **Create an API key** 2. **Create an application key** 3. **Configure the integration in Tidal Control** ## Step 1: Create an API key - Log in to your Datadog account - Click your **organisation name** in the bottom-left corner - Select **Organisation Settings** - Navigate to **API Keys** in the left sidebar - Click **New Key** - Enter a name (e.g. `Tidal Control`) - Click **Create Key** - **Copy the key value**: it is only shown once > **warning:** **Save the API key immediately.** Datadog only shows the full key value once at creation. If you close the dialog without copying it, you will need to create a new key. ## Step 2: Create an application key Datadog uses application keys to authorise access to specific data. The application key controls what the integration can read. - Stay in **Organisation Settings** - Navigate to **Application Keys** in the left sidebar - Click **New Key** - Enter a name (e.g. `Tidal Control`) - Click **Create Key** - **Copy the key value**: it is only shown once > **info:** **Scoped application keys:** Datadog allows you to restrict application keys to specific permissions. If you use scoped keys, make sure the key has read access to: users, monitors, organisation settings, API keys, application keys, security monitoring rules, CSM findings, and Synthetics tests. An unscoped key will work with full read access. ## Step 3: Configure the integration in Tidal Control - Go to **Settings → Integrations** in Tidal Control - Click the **plus icon** next to **Datadog** - Fill in the configuration: - **Name:** A descriptive name, e.g. `Datadog` - **API Key:** The API key from step 1 - **Application Key:** The application key from step 2 - **Site:** Leave blank if your organisation uses the default US region (`datadoghq.com`). Enter your site if you use a different Datadog region (see below) - Click **"Create"** to save the integration ## Configuration fields explained The integration dialog asks for the following values: **Name:** - A descriptive name for this connection - For example: `Datadog`, `Datadog Production` **API Key:** - Identifies your Datadog organisation - Created in step 1 - Keep this value secure **Application Key:** - Authorises Tidal Control to read data from your Datadog account - Created in step 2 - Keep this value secure **Site (optional):** - The Datadog regional site your organisation uses - Leave blank to use the default (`datadoghq.com`) - Enter only the domain, without `https://` (e.g. `datadoghq.eu`, not `https://datadoghq.eu`)
SiteRegion
datadoghq.comUS1 (default)
datadoghq.euEU
us3.datadoghq.comUS3
us5.datadoghq.comUS5
ap1.datadoghq.comAP1 (Asia Pacific)
ap2.datadoghq.comAP2 (Australia)
ddog-gov.comUS1-FED (US Government)
## Verification The integration is working when all of the following are true: - Settings → Integrations shows Datadog under **Configured Integrations** - Datadog tests are available in the Tests section - Test refresh delivers results without authentication errors ## Frequently asked questions **Can I use the same API key and application key for multiple Tidal Control environments?** Yes, you can reuse the same keys across different Tidal Control instances. **Where do I find my Datadog site?** Check the URL when logged in to Datadog. If you use `app.datadoghq.eu`, your site is `datadoghq.eu`. If you use `app.datadoghq.com`, leave the site field blank. **Do I need to be a Datadog admin to create keys?** You need sufficient permissions in Datadog to create API keys and application keys. Typically this requires an admin or owner role in your Datadog organisation. ## Common problems **"The Datadog API key does not have the required permissions"** - Check that both the API key and application key are entered correctly - If you use a scoped application key, verify it has read access to the required data types - Try creating a new unscoped application key to confirm the connection works **"Site must not include a protocol prefix"** - Remove `https://` or `http://` from the site field - Enter only the domain, for example `datadoghq.eu` **"Site must be one of..."** - Check that the site value exactly matches one of the supported site domains listed in the configuration fields table above ### Still can't figure it out? Send an email to support@tidalcontrol.com, and we'll get back to you as soon as possible. > **info:** **Gather support info:** Note which browser you're using, exact error messages, and which steps you've already tried. This speeds up the solution considerably.