Skip to content

ECI-1923 add section about stack destroy issues to troubleshooting docs #39678

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
johannzhang8 merged 2 commits into from
Sep 3, 2026
+33 −0
Merged

ECI-1923 add section about stack destroy issues to troubleshooting docs #39678

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4fb0ce4
add section about stack destroy issues
johannzhang8 Sep 2, 2026
09f24f3
make list, formatting changes
johannzhang8 Sep 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions hugo/content/en/integrations/guide/oci-integration-troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,6 +78,37 @@ Complete the following checks for each monitored region:
3. If you use custom subnets, verify that they meet the [permissions][7] (detailed in the note after step 5).
4. 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.

## OCI stack destroy issues

If the destroy job fails or is unable to be run:

1. Clone the [OCI integration repository][11] and enter the repository directory.
2. Use the [OCI integration cleanup script][10] to remove the remaining resources.
3. Set the required variables.
4. Review a dry run:

```shell
export OCI_PROFILE="<YOUR_OCI_PROFILE>"
export COMPARTMENT_OCID="<YOUR_COMPARTMENT_OCID>"
export TENANCY_OCID="<YOUR_TENANCY_OCID>"

python3 oci-integration-cleanup/integration_cleanup.py \
--profile "$OCI_PROFILE" \
--compartment-ocid "$COMPARTMENT_OCID" \
--dry-run true
```

5. Review the resources planned for deletion in the dry run output. If the output looks correct, execute the cleanup:

```shell
python3 oci-integration-cleanup/integration_cleanup.py \
--profile "$OCI_PROFILE" \
--compartment-ocid "$COMPARTMENT_OCID" \
--confirm-tenancy-id "$TENANCY_OCID" \
--region-workers <number of regions to be processed in parallel> \
--dry-run false
```

## 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][8].
Expand All @@ -93,3 +124,5 @@ Still need help? Contact [Datadog support][3].
[7]: https://docs.datadoghq.com/integrations/oracle-cloud-infrastructure/#deploy-the-quickstart-orm-stack
[8]: /integrations/oracle-cloud-infrastructure/#update-the-integration
[9]: https://app.datadoghq.com/organization-settings/application-keys
[10]: https://github.com/DataDog/oracle-cloud-integration/tree/master/oci-integration-cleanup#readme
[11]: https://github.com/DataDog/oracle-cloud-integration
Loading