From d2dced35aca59f531940f3daa6d6a7d8444dd2dc Mon Sep 17 00:00:00 2001 From: Bryce Eadie Date: Fri, 2 Jan 2026 16:08:31 -0800 Subject: [PATCH 1/6] [DOCS-12864] Add OCI billing guide --- config/_default/menus/main.en.yaml | 11 +++-- content/en/account_management/billing/oci.md | 52 ++++++++++++++++++++ 2 files changed, 60 insertions(+), 3 deletions(-) create mode 100644 content/en/account_management/billing/oci.md diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml index 6eee19b60e8..dff7e8b61a9 100644 --- a/config/_default/menus/main.en.yaml +++ b/config/_default/menus/main.en.yaml @@ -9032,21 +9032,26 @@ menu: url: account_management/billing/google_cloud/ parent: account_management_billing weight: 1316 + - name: + identifier: account_management_billing_oci + url: account_management/billing/oci/ + parent: account_management_billing + weight: 1317 - name: Alibaba Integration identifier: account_management_billing_alibaba url: account_management/billing/alibaba/ parent: account_management_billing - weight: 1317 + weight: 1318 - name: vSphere Integration identifier: account_management_billing_vsphere url: account_management/billing/vsphere/ parent: account_management_billing - weight: 1318 + weight: 1319 - name: Workflow Automation identifier: account_management_billing_workflow_automation url: account_management/billing/workflow_automation/ parent: account_management_billing - weight: 1319 + weight: 1320 - name: Multi-org Accounts identifier: account_management_multi_org_accounts url: account_management/multi_organization/ diff --git a/content/en/account_management/billing/oci.md b/content/en/account_management/billing/oci.md new file mode 100644 index 00000000000..70c907fa142 --- /dev/null +++ b/content/en/account_management/billing/oci.md @@ -0,0 +1,52 @@ +--- +title: Oracle Cloud Infrastructure Integration Billing +--- + +## Overview + +Datadog bills for hosts running the Datadog Agent and all Oracle Cloud Infrastructure (OCI) Compute instances detected by the OCI integration. You are not billed twice if the Datadog Agent runs on a Compute instance that is also detected by the OCI integration. + +Other OCI resources—such as Autonomous Database, Object Storage, Load Balancer, and other managed services—do not impact monthly infrastructure billing. These services can send metrics to Datadog through the integration without additional host charges. + +If you run containers on OCI (for example, on Oracle Kubernetes Engine), container usage is billed separately. See the [containers billing guide][6] for details. + +## OCI metric exclusion + +Use the Datadog–OCI integration tile to control which resources Datadog collects metrics from: + +1. Open the [OCI integration tile][1]. +2. Go to the **Metric Collection** tab. +3. For each connected tenancy, optionally: + - Limit metric collection to specific compartments or regions. + - Limit metric collection to resources with specific [tags][2] using `key:value` pairs. + +When you add or change limits for an existing OCI tenancy, previously discovered Compute instances can remain in the [Infrastructure List][3] for up to two hours while filters propagate. During this transition period, affected instances can display a status of `???`. This does not count towards your billing. + +Hosts with a running Datadog Agent continue to be included in billing. Limiting metric collection in the OCI integration tile applies to instances discovered by the integration and does not exclude hosts that report directly through the Agent. + +## Check if a host is monitored by the Agent or OCI + +In the Infrastructure Host list: + +- Monitored by OCI integration + + If a host displays only the OCI logo, or if its metrics are limited to `oci.*` namespaces, the host is monitored exclusively through the OCI integration. + +- Monitored by the Datadog Agent + + If a host displays the Datadog Agent logo but not the OCI logo, or if its metrics include Agent-collected namespaces (such as `datadog.*`, `system.*`, and others), the host is monitored by the Datadog Agent. + +## Troubleshooting + +For technical questions, contact [Datadog support][4]. + +For billing questions, contact your [Customer Success][5] Manager. + +[1]: https://app.datadoghq.com/integrations?integrationId=oracle-cloud-infrastructure +[2]: /getting_started/tagging/using_tags/#integrations +[3]: /infrastructure/ +[4]: /help/ +[5]: mailto:success@datadoghq.com +[6]: /account_management/billing/containers/ + + From ccbb5302ba63d202a1e8a2d5bc48c1cf4adaa861 Mon Sep 17 00:00:00 2001 From: Bryce Eadie Date: Fri, 2 Jan 2026 16:15:19 -0800 Subject: [PATCH 2/6] [DOCS-12864] Address Vale warnings --- content/en/account_management/billing/oci.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/account_management/billing/oci.md b/content/en/account_management/billing/oci.md index 70c907fa142..24fd7e9806e 100644 --- a/content/en/account_management/billing/oci.md +++ b/content/en/account_management/billing/oci.md @@ -12,7 +12,7 @@ If you run containers on OCI (for example, on Oracle Kubernetes Engine), contain ## OCI metric exclusion -Use the Datadog–OCI integration tile to control which resources Datadog collects metrics from: +Use the OCI integration tile to control which resources Datadog collects metrics from: 1. Open the [OCI integration tile][1]. 2. Go to the **Metric Collection** tab. @@ -20,7 +20,7 @@ Use the Datadog–OCI integration tile to control which resources Datadog collec - Limit metric collection to specific compartments or regions. - Limit metric collection to resources with specific [tags][2] using `key:value` pairs. -When you add or change limits for an existing OCI tenancy, previously discovered Compute instances can remain in the [Infrastructure List][3] for up to two hours while filters propagate. During this transition period, affected instances can display a status of `???`. This does not count towards your billing. +When you add or change limits for an existing OCI tenancy, previously discovered Compute instances can remain in the [Infrastructure List][3] for up to two hours while filters propagate. During this transition period, affected instances can display a status of `???`. This does not count toward your billing. Hosts with a running Datadog Agent continue to be included in billing. Limiting metric collection in the OCI integration tile applies to instances discovered by the integration and does not exclude hosts that report directly through the Agent. From 724ee2e3a228b43008b18a1e1c2c769c9e2dff06 Mon Sep 17 00:00:00 2001 From: Bryce Eadie Date: Fri, 2 Jan 2026 16:59:51 -0800 Subject: [PATCH 3/6] [DOCS-12864] Fix menu entry --- config/_default/menus/main.en.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml index dff7e8b61a9..2eff5da833d 100644 --- a/config/_default/menus/main.en.yaml +++ b/config/_default/menus/main.en.yaml @@ -9032,7 +9032,7 @@ menu: url: account_management/billing/google_cloud/ parent: account_management_billing weight: 1316 - - name: + - name: OCI Integration identifier: account_management_billing_oci url: account_management/billing/oci/ parent: account_management_billing From 0ba190bb0d9f64b98c05d2118b84669603234162 Mon Sep 17 00:00:00 2001 From: Bryce Eadie Date: Tue, 6 Jan 2026 16:22:26 -0800 Subject: [PATCH 4/6] [DOCS-12864] Update page title --- content/en/account_management/billing/oci.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/account_management/billing/oci.md b/content/en/account_management/billing/oci.md index 24fd7e9806e..4403edb03bb 100644 --- a/content/en/account_management/billing/oci.md +++ b/content/en/account_management/billing/oci.md @@ -1,5 +1,5 @@ --- -title: Oracle Cloud Infrastructure Integration Billing +title: OCI Integration Billing --- ## Overview From f84c7b625223c5a6d22f2e04e74fefc4ac4e7345 Mon Sep 17 00:00:00 2001 From: Bryce Eadie Date: Tue, 13 Jan 2026 17:04:26 -0800 Subject: [PATCH 5/6] Add log exclusion info --- content/en/account_management/billing/oci.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/content/en/account_management/billing/oci.md b/content/en/account_management/billing/oci.md index 4403edb03bb..6791d5b65d1 100644 --- a/content/en/account_management/billing/oci.md +++ b/content/en/account_management/billing/oci.md @@ -18,11 +18,19 @@ Use the OCI integration tile to control which resources Datadog collects metrics 2. Go to the **Metric Collection** tab. 3. For each connected tenancy, optionally: - Limit metric collection to specific compartments or regions. - - Limit metric collection to resources with specific [tags][2] using `key:value` pairs. + +## OCI log exclusion + +Use the OCI integration tile to control which resources Datadog collects logs from: + +1. Open the [OCI integration tile][1]. +2. Go to the **Log Collection** tab. +3. For each connected tenancy, optionally: + - Limit log collection to specific compartments or regions. When you add or change limits for an existing OCI tenancy, previously discovered Compute instances can remain in the [Infrastructure List][3] for up to two hours while filters propagate. During this transition period, affected instances can display a status of `???`. This does not count toward your billing. -Hosts with a running Datadog Agent continue to be included in billing. Limiting metric collection in the OCI integration tile applies to instances discovered by the integration and does not exclude hosts that report directly through the Agent. +Hosts with a running Datadog Agent continue to be included in billing. Limiting metric and log collection in the OCI integration tile applies to instances discovered by the integration and does not exclude hosts that report directly through the Agent. ## Check if a host is monitored by the Agent or OCI @@ -43,7 +51,6 @@ For technical questions, contact [Datadog support][4]. For billing questions, contact your [Customer Success][5] Manager. [1]: https://app.datadoghq.com/integrations?integrationId=oracle-cloud-infrastructure -[2]: /getting_started/tagging/using_tags/#integrations [3]: /infrastructure/ [4]: /help/ [5]: mailto:success@datadoghq.com From db512677768893ec6d5768bdbfc622ccf2858205 Mon Sep 17 00:00:00 2001 From: Bryce Eadie Date: Wed, 14 Jan 2026 13:48:53 -0800 Subject: [PATCH 6/6] Clarify data exclusion options --- content/en/account_management/billing/oci.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/content/en/account_management/billing/oci.md b/content/en/account_management/billing/oci.md index 6791d5b65d1..ddeb1bf6b77 100644 --- a/content/en/account_management/billing/oci.md +++ b/content/en/account_management/billing/oci.md @@ -17,7 +17,9 @@ Use the OCI integration tile to control which resources Datadog collects metrics 1. Open the [OCI integration tile][1]. 2. Go to the **Metric Collection** tab. 3. For each connected tenancy, optionally: - - Limit metric collection to specific compartments or regions. + - Limit metric collection to specific compartments. + +**Note**: You can exclude OCI regions from all data collection (metrics and logs) on the **General** tab of the OCI integration tile. ## OCI log exclusion @@ -26,7 +28,9 @@ Use the OCI integration tile to control which resources Datadog collects logs fr 1. Open the [OCI integration tile][1]. 2. Go to the **Log Collection** tab. 3. For each connected tenancy, optionally: - - Limit log collection to specific compartments or regions. + - Limit log collection to specific compartments. + +**Note**: You can exclude OCI regions from all data collection (metrics and logs) on the **General** tab of the OCI integration tile. When you add or change limits for an existing OCI tenancy, previously discovered Compute instances can remain in the [Infrastructure List][3] for up to two hours while filters propagate. During this transition period, affected instances can display a status of `???`. This does not count toward your billing.