OCI Integration Troubleshooting
To find out if this integration is available in your organization, see your Datadog Integrations page or ask your organization administrator.
To initiate an exception request to enable this integration for your organization, email support@ddog-gov.com.
Overview
Use this guide to troubleshoot issues related to the Datadog OCI Integration.
Integration issues
See configuration issues with your OCI integration on the Issues tab of the OCI integration tile.
Invalid Datadog API or app key credentials
This occurs when the Datadog API key or application key configured in the OCI integration has expired or is invalid. Both keys are validated during a stack apply. Look for the following error in your ORM stack’s job logs to confirm:
Error: unexpected response code '403': {"errors":["Forbidden"]}
with module.integration[0].restapi_object.datadog_tenancy_integration,
on modules/integration/main.tf line 15, in resource "restapi_object" "datadog_tenancy_integration":
15: resource "restapi_object" "datadog_tenancy_integration" {
To remediate this, generate new credentials and update your integration deployment:
- Go to API Keys in your Datadog organization settings and generate a new API key.
- Go to Application Keys in your Datadog organization settings and generate a new application key.
- Update your integration deployment with the new keys and reapply it.
- Navigate to Oracle Resource Manager stacks and locate your Datadog QuickStart stack.
- Click Edit on the stack.
- Click Next to reach the Configure Variables page.
- Update the Datadog API Key and Datadog Application Key values with the new credentials.
- Click Next.
- Click Save changes.
- Update the
datadog_api_key and datadog_app_key values in your Terraform .tf file with the new credentials. - Run
terraform apply to apply the updated configuration.
Required OCI IAM permissions are missing
Datadog has received a 403 error when querying OCI, indicating that not all necessary IAM permissions have been granted.
Check the Policies page in OCI to ensure that the dd-svc-policy and dd-dynamic-group policies have all read-only permissions properly configured.
OCI tenancy reaching service connector hub limit
For each tenancy, at least one service connector hub is required per five compartments. Request a service limit increase in your OCI account.
Cannot collect data from one or more subscribed regions
The application function used to forward Datadog metrics and logs was not found.
To remediate this, reapply the existing Datadog integration ORM Stack in your OCI tenancy.
Note: If you specified the subnet OCIDs in the optional configuration section, ensure that there is one subnet OCID per subscribed region. Do not make any other modifications to the existing stack before reapplying it.
Metrics not being collected
Complete the following checks for each monitored region:
- In the integration compartment, verify that the
dd-function-app function application exists. - In
dd-function-app, verify that the dd-metrics-forwarder function exists. - If you use custom subnets, verify that they meet the permissions (detailed in the note after step 5).
- For each Datadog-created metric service connector hub, confirm that its function target is the
dd-metrics-forwarder function in dd-function-app. Datadog-created metric connector hubs use the format dd-metrics-connectorhub-<suffix>. If a connector hub targets a different forwarding function application, delete it and allow it to be automatically reprovisioned.
Outdated integration version
This occurs when your Datadog integration ORM stack or Terraform module is out of date. To remediate this, update your deployment to the latest version and reapply it. For instructions covering both QuickStart (ORM stack) and Terraform, see Update the integration.
Still need help? Contact Datadog support.