---
title: OVHcloud
description: Monitor your OVHcloud infrastructure logs in Datadog
breadcrumbs: Docs > Integrations > OVHcloud
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# OVHcloud
Supported OS Integration version1.0.0
{% callout %}
# Important note for users on the following Datadog sites: app.ddog-gov.com, us2.ddog-gov.com

{% alert level="danger" %}
This product is not supported for your selected [Datadog site](https://docs.datadoghq.com/getting_started/site.md). ({% placeholder "user-datadog-site-name" /%}).
{% /alert %}

{% /callout %}
  An overview of logs captured from OVHcloudAn overview of HTTP logs captured from OVHcloud
## Overview{% #overview %}

Use this integration to collect logs from [OVHcloud Logs Data Platform](https://www.ovhcloud.com/en/logs-data-platform/) (LDP) and forward them to Datadog. After ingestion, you can search, filter, and monitor your OVHcloud logs in [Datadog Log Management](https://docs.datadoghq.com/logs.md).

## Setup{% #setup %}

### Prerequisites{% #prerequisites %}

Before you begin, make sure you have:

- An OVHcloud account
- An active [Logs Data Platform](https://www.ovhcloud.com/en/logs-data-platform/) (LDP) service with IAM enabled and at least one data stream subscribed to an alias
- An OVHcloud service account with an IAM policy that grants read access to your LDP aliases
- A Datadog account with permission to configure integrations

For LDP setup instructions, see the [OVHcloud LDP documentation](https://help.ovhcloud.com/csm/en-logs-data-platform-getting-started). If your service uses legacy token-based authentication, follow the [IAM migration guide](https://help.ovhcloud.com/csm/en-logs-data-platform-iam-migration). For IAM policy setup, see [IAM for Logs Data Platform](https://help.ovhcloud.com/csm/en-gb-logs-data-platform-iam-access-management?id=kb_article_view&sysparm_article=KB0071653).

### OVHcloud LDP configuration{% #ovhcloud-ldp-configuration %}

Before enabling log collection, create a service account in OVHcloud and grant it access to your LDP streams:

1. In the OVHcloud Control Panel, navigate to **Identities** > **Service accounts** and add a service account. Save the generated **Name** and **Password**.

1. Create an IAM policy and attach the service account to it.

1. Select the **Logs Data Platform: Alias** product type.

1. Add one or more aliases to the resource list, or add an applicable resource group.

1. Add the following actions to allow Datadog to read from those aliases:

   ```
   ldp:apiovh:output/opensearch/alias/get
   ldp:apiovh:output/opensearch/alias/index/get
   ldp:apiovh:output/opensearch/alias/stream/get
   ldp:apiovh:output/opensearch/alias/url/get
   ldp:opensearch:alias/read
   ```

### Datadog configuration{% #datadog-configuration %}

1. Go to the [OVHcloud integration tile](https://app.datadoghq.com/integrations/ovhcloud) in Datadog.
1. Click **Add Account**.
1. Enter an account name.
1. Select your **API zone**:
   - `OVH Europe (ovh-eu)` for the European API
   - `OVH US (ovh-us)` for the US API
   - `OVH Canada (ovh-ca)` for the Canadian API
1. Enter the **Access point** hostname for your LDP cluster. You can find this in the OVHcloud LDP console under your cluster details (for example, `gra2.logs.ovh.com`).
1. Enter your **LDP ID**. You can find this on your LDP service overview page (for example, `ldp-ra-xxxxx`).
1. (Optional) Enter one or more **Aliases** to ingest. Leave this field empty to ingest logs from all aliases on the service. Alias names are case-sensitive.
1. Enter the Service User **Name** and **Password** from the service account you created.
1. (Optional) Enter **Account Tags**. This comma-separated list of `<KEY:VALUE>` tags is applied to all metrics, logs, and resources collected from this OVHcloud account.
1. Click **Save**.

**Note**: Datadog polls your LDP OpenSearch endpoint every 10 minutes. Logs appear in Datadog about 10 to 15 minutes after they are written to LDP.

### Validation{% #validation %}

After you save the configuration, wait up to 15 minutes for log collection to begin. Then:

1. Go to the [Log Explorer](https://app.datadoghq.com/logs) in Datadog.
1. Search for `source:ovhcloud` to confirm that logs are flowing.

## Uninstallation{% #uninstallation %}

To stop collecting logs and remove an OVHcloud account from Datadog:

1. Go to the [OVHcloud integration tile](https://app.datadoghq.com/integrations/ovhcloud) in Datadog.
1. From the left panel, select the account you want to remove.
1. Click **Delete Account** at the bottom of the account configuration panel.
1. In the confirmation dialog, click **Confirm**.

Deleting an account stops further log collection for that account. Data that was already collected is not removed from Datadog.

To fully revoke access, delete or disable the service account in the OVHcloud Control Panel after removing the account from Datadog.

## Troubleshooting{% #troubleshooting %}

The following are health errors you might see on your OVHcloud integration tile, and how to resolve them.

### Authentication: Credential issues{% #authentication-credential-issues %}

#### `OVHcloud service account client ID is malformed`{% #ovhcloud-service-account-client-id-is-malformed %}

- **Type**: 400 Bad Request from the OVHcloud API; auth issue
- **Description**: The IAM bearer-token request was rejected because the service account client ID configured on the OVHcloud integration tile is not a valid 16-character hexadecimal string, with or without a US/EU/CA region prefix. The client ID must be 16 hex characters, optionally prefixed with `US.`, `EU.`, or `CA.`.
- **Remediation**:
  1. Navigate to your OVHcloud integration tile in Datadog
  1. Re-enter the service account client ID. The client ID is a 16-character hexadecimal string, optionally prefixed with the API zone (US, EU, or CA) followed by a dot - e.g., `f0f0f0f0f0f0f0f0` or `US.f0f0f0f0f0f0f0f0`
  1. Wait ~10 minutes for the fix to show up on your integration tile

#### `OVHcloud API zone does not match the service account client ID region`{% #ovhcloud-api-zone-does-not-match-the-service-account-client-id-region %}

- **Type**: 400 Bad Request from the OVHcloud API; auth issue
- **Description**: The client ID is validly formatted with a region prefix (e.g., `US.…`), but the API Zone selected on the tile was changed to a different zone (e.g., `ovh-EU`). The region embedded in the client ID no longer matches the configured zone.
- **Remediation**:
  1. Navigate to your OVHcloud integration tile in Datadog
  1. Update the API zone so it matches the region prefix of the service account IAM Service Account Name (US, EU, or CA). For example, a client ID prefixed with `US.` requires the ovh-US API zone
  1. Wait ~10 minutes for the fix to show up on your integration tile

#### `OVHcloud service account no longer exists`{% #ovhcloud-service-account-no-longer-exists %}

- **Type**: 400 Bad Request from the OVHcloud API; auth issue
- **Description**: The service account referenced by the configured client ID has been deleted from the OVHcloud console, so the IAM bearer-token request fails.
- **Remediation**: Verify the client ID, client secret, and API zone configured on the OVHcloud integration tile are correct
  1. Navigate to your OVHcloud Control Panel
  1. At the top right, set the navigation view to **Alternative Navigation** or **Navigation (beta)**
  1. **Identify, Security, & Operations** > **Identities** > **Service account**
  1. Click **Add a service account**
  1. Enter a name & description
  1. Save your service account name and password in a safe place
  1. In the **OVHcloud Control Panel** > **Identify, Security, & Operations** > **Policies** > **My policies** > **Choose your policy**
  1. **Service accounts** > **Add service accounts**
  1. Add the service account created above
  1. Click **Modify policy**
  1. Navigate to your OVHcloud integration tile in Datadog
  1. **IAM Service Account Name** > **Update Secret** using the service account name you saved for your new service account
  1. **IAM Service Account Password** > **Update Secret** using the password you saved for your new service account
  1. Wait ~10 minutes for the fix to show up on your integration tile

#### `OVHcloud service account client secret is too short`{% #ovhcloud-service-account-client-secret-is-too-short %}

- **Type**: 403 Forbidden from the OVHcloud API; auth issue
- **Description**: The IAM bearer-token request was rejected because the service account client secret (the OAuth2 password) entered on the tile is shorter than the expected 32-character length, indicating a truncated or wrong secret.
- **Remediation**:
  1. Navigate to your OVHcloud integration tile in Datadog
  1. Re-enter the service account client secret (**IAM Service Account Password** > **Update Secret**). OVHcloud displays the secret only once at service account creation - if you no longer have it, create a new service account, grant it Logs Data Platform read access, and update the tile with its credentials
  1. Wait ~10 minutes for the fix to show up on your integration tile

### Logs Data Platform (LDP): Search issues{% #logs-data-platform-ldp-search-issues %}

#### `OVHcloud Logs Data Platform access point is malformed`{% #ovhcloud-logs-data-platform-access-point-is-malformed %}

- **Type**: URL parse error (no HTTP response sent); configuration issue
- **Description**: The access point entered on the tile contains characters illegal in a URL host, so the search request cannot be constructed - no HTTP response is ever sent.
- **Remediation**:
  1. Navigate to your OVHcloud integration tile in Datadog
  1. Re-enter the Logs Data Platform access point. It is a hostname such as `bhs2.logs.ovh.com` found in the OVHcloud Logs Data Platform console; it must not contain spaces or other characters illegal in a URL host
  1. Wait ~10 minutes for the fix to show up on your integration tile

#### `OVHcloud Logs Data Platform access point is unreachable`{% #ovhcloud-logs-data-platform-access-point-is-unreachable %}

- **Type**: No HTTP response (transport failure); configuration issue
- **Description**: The access point is a syntactically plausible hostname that does not resolve or refuses connections , so the transport fails before any HTTP response is received.
- **Remediation**:
  1. Navigate to your OVHcloud integration tile in Datadog
  1. Verify the Logs Data Platform access point. It is a hostname such as `bhs2.logs.ovh.com` found in the OVHcloud Logs Data Platform console; a value that does not resolve or refuses connections produces no HTTP response
  1. Wait ~10 minutes for the fix to show up on your integration tile

#### `OVHcloud Logs Data Platform ID is not a valid LDP ID`{% #ovhcloud-logs-data-platform-id-is-not-a-valid-ldp-id %}

- **Type**: 403 Forbidden from the OVHcloud API; configuration issue
- **Description**: The LDP ID on the tile does not match the `ldp-<xx>-<xxxxx>` format (e.g., `ldp-ab-12345`), so the search returns 403. Checked before alias validity.
- **Remediation**:
  1. Navigate to your OVHcloud integration tile in Datadog
  1. Re-enter a valid LDP ID (format `ldp-<xx>-<xxxxx>`, e.g., `ldp-ab-12345`) found in the OVHcloud Logs Data Platform console
  1. Wait ~10 minutes for the fix to show up on your integration tile

#### `OVHcloud Logs Data Platform alias is not valid for the configured LDP ID`{% #ovhcloud-logs-data-platform-alias-is-not-valid-for-the-configured-ldp-id %}

- **Type**: 403 Forbidden from the OVHcloud API; configuration issue
- **Description**: One or more aliases on the tile do not conform to `<LDP ID>-a-<name>` (or the alias was deleted on the OVHcloud side). The LDP ID is valid, but the alias is not, so the search returns 403. Checked after LDP ID validity.
- **Remediation**:
  - *If you wish to use the new alias:*
    1. Navigate to your OVHcloud Control Panel
    1. At the top right, set the navigation view to **Alternative Navigation** or **Navigation (beta)**
    1. **Identify, Security, & Operations** > **Logs Data Platform** > **Your LDP ID** (e.g., `ldp-ab-12345`) > **Alias**
    1. Click **Add an alias**
    1. Add an alias with a suffix of your choosing (excluding `ldp-ab-12345-a-`), with any description. (e.g., enter `example-suffix` to generate the alias `ldp-ab-12345-a-example-suffix`)
    1. Click **Save**
    1. Wait ~10 minutes for the fix to show up on your integration tile
  - *If you don't wish to use the new alias:*
    1. Navigate to the account you wish to fix
    1. Under "Logs Data Platform Aliases," remove the alias you no longer wish to use
    1. Click **Save Changes**
    1. Wait ~10 minutes for the fix to show up on your integration tile

#### `OVHcloud Logs Data Platform search is forbidden`{% #ovhcloud-logs-data-platform-search-is-forbidden %}

- **Type**: 403 Forbidden from the OVHcloud API; token issue
- **Description**: The catch-all for a 403 from the search call once the LDP ID and aliases have been validated as well-formed. The bearer token was accepted, but the service account's policy is missing, removed from a policy, lacks the `ldp:opensearch:alias/read` permission, or has its resource group (e.g., `ovh-default`) removed.
- **Remediation**:
  1. Navigate to your OVHcloud Control Panel
  1. At the top right, set the navigation view to **Alternative Navigation** or **Navigation (beta)**
  1. **Identify, Security, & Operations** > **Policies** > **My policies**
  1. Ensure your policy exists on Logs Data Platform
  1. Verify the OVHcloud service account is listed in it
  1. Verify it retains the `ldp:opensearch:alias/read` permission
  1. Verify the correct resource groups are attached to the policy
  1. Wait ~10 minutes for the fix to show up on your integration tile

#### `OVHcloud Logs Data Platform alias search failed`{% #ovhcloud-logs-data-platform-alias-search-failed %}

- **Type**: 400 Bad Request from the OVHcloud API; configuration issue
- **Description**: The alias exists and is readable, but a stream it points at holds no searchable log data - e.g., a metrics index (`ldp-ab-12345-i-vm-metrics-test`) attached to the alias has no timestamp field, so OpenSearch returns a 400 `query_shard_exception`.
- **Remediation**:
  - *If you wish to use the new alias:*
    1. Remove the index ID (e.g., `ldp-ab-12345-i-vm-metrics-test`) from the index list
    1. Wait ~10 minutes for the fix to show up on your integration tile
  - *If you don't wish to use the new alias:*
    1. Delete the alias
    1. Wait ~10 minutes for the fix to show up on your integration tile

## Support{% #support %}

Need help? Contact [Datadog Support](https://app.datadoghq.com/help).