Overview

Use this guide to troubleshoot the Datadog Alibaba Cloud integration. Configuration issues appear on the Alibaba Cloud integration tile.

Alibaba Cloud access key is invalid or no longer exists

This issue occurs when the access key ID or access key secret configured for the integration is invalid, inactive, or deleted.

To remediate this issue:

• If the access key is inactive, re-enable it in the Alibaba Cloud RAM console.
• If the access key secret is invalid, update the Datadog integration with the correct secret.
• If the access key no longer exists, or the correct secret is unavailable, create a replacement access key for the RAM user that Datadog uses. Copy the new key ID and secret, then update the Alibaba Cloud credentials in the Datadog integration. For instructions, see Create an AccessKey pair in the Alibaba Cloud documentation.

Then confirm that the RAM user has the permissions required by the Alibaba Cloud integration.

Cloud monitoring permissions are missing

This issue occurs when the RAM user used by the Datadog integration cannot query CloudMonitor metrics.

To remediate this issue, add the cms:DescribeMetricList permission to the policy attached to the Datadog integration RAM user. Then wait about 15 minutes for the next collection cycle to confirm that Datadog receives CloudMonitor metrics.

For instructions on editing a RAM policy, see Grant permissions to a RAM user.

Log collection permissions are missing

This issue occurs when the RAM user used by the Datadog integration lacks the permissions required to read from Simple Log Service (SLS).

To remediate this issue:

1. Review the policy attached to the Datadog integration RAM user.
2. Add the SLS read permissions described in SLS RAM access control permissions.
3. Confirm that the policy applies to every SLS project and logstore that you want Datadog to collect logs from.

For instructions on editing a RAM policy, see Grant permissions to a RAM user.

Prometheus permissions for ACK are missing

This issue occurs when the RAM user used by the Datadog integration lacks the permissions required to configure Alibaba Cloud Managed Service for Prometheus on an Alibaba Cloud Container Service for Kubernetes (ACK) cluster.

To remediate this issue, add the following permissions to the policy attached to that RAM user. Scope the policy to the intended clusters where possible. The policy must include at least:

• cs:InstallClusterAddons
• cs:UnInstallClusterAddons

These permissions allow Datadog to install and reinstall the ack-arms-prometheus add-on on ACK clusters.

For instructions on editing a RAM policy, see Grant permissions to a RAM user. For resource-scoping options, see InstallClusterAddons.

Alibaba Cloud Resource Center is not enabled

This issue occurs when Alibaba Cloud Resource Center is not enabled for the account. Datadog cannot collect metrics until you enable the service.

To remediate this issue:

1. Sign in to the Alibaba Cloud account that is connected to Datadog.
2. Open Resource Center.
3. Enable Resource Center for the account.
4. Attach the AliyunResourceCenterReadOnlyAccess policy to the Datadog integration RAM user.
5. Wait about 15 minutes for the next collection cycle to confirm that Datadog receives metrics.

Alibaba Cloud API quota limit reached

This issue occurs when the account has reached an Alibaba Cloud API quota limit. This is distinct from temporary request throttling.

To remediate this issue:

1. Review the quota and billing status for the Alibaba Cloud account.
2. If applicable, enable pay-as-you-go quotas or resolve outstanding billing issues.
3. If the existing quota is insufficient, request a quota increase.
4. Wait for the quota change to take effect, then confirm that Datadog resumes collection.

Still need help? Contact Datadog support.