--- title: Getting Started with Oracle Cloud Infrastructure (OCI) description: >- Integrate your Oracle Cloud Infrastructure environment with Datadog for comprehensive monitoring breadcrumbs: >- Docs > Getting Started > Introduction to Integrations > Getting Started with Oracle Cloud Infrastructure (OCI) --- # Getting Started with Oracle Cloud Infrastructure (OCI) ## Overview{% #overview %} Use this guide to get started with monitoring your Oracle Cloud Infrastructure (OCI) environment. Datadog's QuickStart setup simplifies the integration process, automatically provisioning the infrastructure needed to collect metrics, logs, and resource data from your OCI tenancy. {% collapsible-section #prerequisites %} #### Prerequisites ### In OCI{% #in-oci %} Your OCI user account needs the following: - The **Identity Domain Administrator** role - Ability to create a user, user group, and dynamic group in the Identity Domain - Ability to create policies in the root compartment You must also: - Be logged into the tenancy you want to integrate - Have the Home Region selected in the OCI console **Note**: The OCI integration is restricted to one integration per tenancy. All OCI Commercial regions (in the OC1 realm) that existed as of January 1, 2026 are supported. ### In Datadog{% #in-datadog %} A [Datadog account](https://www.datadoghq.com/) with [permissions to create API and application keys](https://docs.datadoghq.com/account_management/rbac/permissions/#api-and-application-keys). {% /collapsible-section %} ## Setup{% #setup %} Datadog's QuickStart for OCI is a fully managed setup experience that provisions all necessary infrastructure in your tenancy. The setup automatically creates Oracle Service Connector Hubs to stream metrics and logs to Datadog, and continuously discovers new resources and compartments as your environment grows. **Note**: Before starting, consider [requesting a service limit increase](https://docs.oracle.com/iaas/Content/General/Concepts/servicelimits.htm#Requesti) for Service Connector Hubs. The approximate number needed is: $$\text"Service Connector Hubs" = \text"Number of compartments in tenancy" / \text"5"$$ ### Configure the Datadog OCI integration tile{% #configure-the-datadog-oci-integration-tile %} 1. Go to the [Datadog OCI integration tile](https://app.datadoghq.com/integrations/oracle-cloud-infrastructure) and click **Add New Tenancy**. 1. Select or create a Datadog API key to use for the integration. 1. Create a Datadog application key. 1. Enable or disable logs using the toggle. 1. Click **Create OCI Stack**. This opens the Oracle Resource Manager in the OCI console to complete deployment. **Note**: Deploy this stack only once per tenancy. ### Deploy the QuickStart ORM stack{% #deploy-the-quickstart-orm-stack %} 1. In the OCI console, accept the Oracle Terms of Use. 1. Leave the option to use custom Terraform providers unchecked. 1. Use the default working directory, or optionally choose a different one. 1. Click **Next**. 1. Leave the **(Optional) Choose specific subnet(s)** section blank. QuickStart automatically creates a new Virtual Cloud Network (VCN) and subnet in each region, providing the simplest setup. **Advanced option**: To use existing subnets (maximum of one per OCI region), provide the subnet OCIDs (one per line, without commas). Format: `ocid1.subnet.oc[0-9].*`. Example: `ocid1.subnet.oc1.iad.abcedfgh`. If you're using existing subnets, ensure each VCN has HTTP egress through NAT Gateway, a Service Gateway for "All Services In Oracle Services Network", appropriate route table rules, and security rules for HTTP requests. 1. Leave the **(Optional) Choose a User** section blank. QuickStart creates a new Group and User in your current OCI Identity Domain, simplifying IAM setup. **Advanced option**: To use an existing Group and User, provide both the **Group ID** and **User ID** OCIDs. The user must be a member of the specified group. 1. Leave the **(Optional) Advanced configuration** section blank for most use cases. **Advanced options**: - **Compartment**: Specify an existing compartment for Datadog-created resources (default creates a new "Datadog" compartment). - **Domain**: Provide an Identity Domain OCID to override where the User and Group are created. Requires the **Identity Domain Administrator** role in that domain. - **Resource tags**: Provide a list of defined tags to be added to all OCI resources deployed by the Datadog QuickStart stack. Enter one tag per line. Do not add commas. Each defined tag should be in the format: `namespace.key:value`. For example, `CostCenter.Environment:prod`. If left blank, no defined tags are added to the OCI resources deployed by the Datadog QuickStart stack. 1. Click **Next**. 1. Click **Create**, and wait up to 30 minutes for the deployment to complete. ### Complete the setup in Datadog{% #complete-the-setup-in-datadog %} Return to the [Datadog OCI integration tile](https://app.datadoghq.com/integrations/oracle-cloud-infrastructure) and click **Ready!** ### Validation{% #validation %} Wait up to 10 minutes for data to start being collected, and then view `oci.*` metrics in the [OCI integration overview dashboard](https://app.datadoghq.com/dash/integration/31417/oracle-cloud-infrastructure-oci-overview) or [Metrics Explorer page](https://app.datadoghq.com/metric/explorer) in Datadog. {% image source="https://datadog-docs.imgix.net/images/getting_started/integrations/oci/oci-dashboard.eabd2139d2ff7827e7280b314af90d76.png?auto=format" alt="The OCI overview dashboard in Datadog with various metrics and graphs from Oracle Cloud Infrastructure services" /%} {% alert level="info" %} OCI function metrics (`oci.faas` namespace) and container instance metrics (`oci_computecontainerinstance` namespace) are in Preview. {% /alert %} ## Configuration{% #configuration %} After completing the setup, a configuration tab for the tenancy becomes available on the left side of the [Datadog OCI integration tile](https://app.datadoghq.com/integrations/oracle-cloud-infrastructure). Apply tenancy-wide data collection configurations as outlined below. ### Add regions{% #add-regions %} On the **General** tab, select the regions for data collection from the **Regions** checkbox list. Region selections apply to the entire tenancy, for both metrics and logs. **Note**: If you used the QuickStart setup method, and afterward subscribed to a new OCI region, reapply the initial setup stack in ORM. The new region then becomes available in the Datadog OCI tile. ### Metric and log collection{% #metric-and-log-collection %} Use the **Metric collection** and **Log collection** tabs to configure which metrics and logs are sent to Datadog. **Note**: Filters are evaluated in order: **Selected Services** acts as the primary toggle for data collection from a service, then compartment tag filters are applied, and finally resource tag filters. #### Enable or disable all collection{% #enable-or-disable-all-collection %} Both the metric and log collection tabs have a main toggle to disable collection of that data type for the entire tenancy. #### Limit collection to specific OCI services{% #limit-collection-to-specific-oci-services %} Use the **Selected Services** section to enable or disable collection from individual OCI services. Disabling a service stops all collection from it, regardless of any resource tag filters configured for it. When a service is enabled, resource tag filters can further narrow collection to specific resources within that service. Resources without a matching inclusion tag are excluded. **Note**: Service toggle changes may take up to 5 minutes to take effect. {% collapsible-section #tag-filter-syntax %} ##### Tag filter syntax The **Compartment Tags** and **Limit Collection to Specific Resources** sections accept comma-separated `key:value` OCI tags. Prefix a tag with `!` to negate it. The comma separator behaves differently depending on the tag types used: - **Positive tags only**: OR logic—included if the OCI object has **any** of the listed tags. - **Negative tags only** (prefixed with `!`): OR logic—excluded if **any** of the negated tags is present. - **Mixed positive and negative tags**: AND logic—must satisfy **all** listed conditions to be included. For example: - `datadog:monitored,env:prod*`: include if **either** tag is present. - `!env:staging,!testing:true`: exclude if **either** tag is present. - `datadog:monitored,!region:us-phoenix-1`: include only if the `datadog:monitored` tag is present **and** the `region:us-phoenix-1` tag is absent. {% /collapsible-section %} #### Limit collection by compartment{% #limit-collection-by-compartment %} Use the **Compartment Tags** section to include or exclude specific compartments based on OCI compartment tags. See Tag filter syntax for syntax reference. **Note**: In OCI, tags are not inherited by child compartments; each compartment must be tagged individually. After modifying tags in OCI, it may take up to 15 minutes for the changes to appear in Datadog. #### Limit collection to specific resources{% #limit-collection-to-specific-resources %} Use the **Limit Collection to Specific Resources** section to define which resources send their metrics or logs to Datadog. Select an OCI service from the dropdown, then specify the resource tags to target. See Tag filter syntax for syntax reference. ### Resource collection{% #resource-collection %} On the **Resource Collection** tab of the [Datadog OCI integration tile](https://app.datadoghq.com/integrations/oracle-cloud-infrastructure), click the **Enable Resource Collection** toggle. Resources are visible in the [Datadog Resource Catalog](https://docs.datadoghq.com/infrastructure/resource_catalog/). ## Get more from the Datadog platform{% #get-more-from-the-datadog-platform %} ### Install the Agent for deeper visibility{% #install-the-agent-for-deeper-visibility %} While the OCI integration automatically collects service-level metrics through Oracle Cloud Monitoring, installing the [Datadog Agent](https://docs.datadoghq.com/getting_started/agent/) on your compute instances unlocks deeper infrastructure and application insights: - **System-level metrics** with sub-second granularity for CPU, memory, disk, and network - **Process-level visibility** to understand resource consumption by application - **Custom metrics** from your applications through [DogStatsD](https://docs.datadoghq.com/developers/dogstatsd/?tab=hostagent) - **Distributed traces** for end-to-end request visibility - **Logs** correlated with metrics for faster troubleshooting The Agent installs with a single command for most operating systems, including Oracle Linux. See the [Agent installation page](https://app.datadoghq.com/account/settings/agent/latest) for instructions, or read [why you should install the Agent on cloud instances](https://docs.datadoghq.com/agent/faq/why-should-i-install-the-agent-on-my-cloud-instances/) for more details on the benefits. ### Use the Datadog Agent with OCI Kubernetes Engine (OKE){% #use-the-datadog-agent-with-oci-kubernetes-engine-oke %} For containerized environments on OKE, you can use the [Datadog Agent for Kubernetes](https://docs.datadoghq.com/agent/kubernetes/?tab=helm). Use the dedicated Kubernetes documentation to deploy the Agent in your OKE cluster and collect metrics, logs, and traces from your containerized applications. ## Explore related services{% #explore-related-services %} ### GPU monitoring{% #gpu-monitoring %} Monitoring OCI GPU instances is essential for ensuring optimal performance and reliability of your high-performance computing workloads. The [OCI GPU integration](https://docs.datadoghq.com/integrations/oci_gpu/) provides a comprehensive set of GPU metrics through the `gpu_infrastructure_health` namespace, enabling you to track the health, capacity, throughput, status, and performance of your [GPU instances](https://www.oracle.com/cloud/compute/#gpu). After setting up the OCI integration, ensure that the GPU-related namespaces are included in your metric collection configuration. See the [OCI GPU Overview dashboard](https://app.datadoghq.com/dash/integration/31744/oci-gpu-overview) (created automatically when you set up the OCI GPU integration) for an overview of your GPU infrastructure. ### Cloud Cost Management{% #cloud-cost-management %} Datadog's [Oracle Cloud Cost Management](https://docs.datadoghq.com/cloud_cost_management/setup/oracle/) provides insights for engineering and finance teams to understand how infrastructure changes impact costs, allocate spend across your organization, and identify potential improvements. To enable Cloud Cost Management for OCI: 1. Ensure you have configured the OCI integration as described above. 1. Follow the setup instructions in the [Oracle Cloud Cost Management documentation](https://docs.datadoghq.com/cloud_cost_management/setup/oracle/) to enable cost data collection. ### Cloud SIEM{% #cloud-siem %} Cloud SIEM provides real-time analysis of operational and security logs, using out-of-the-box integrations and rules to detect and investigate threats. To use Cloud SIEM with your OCI environment: 1. Ensure log collection is enabled in your OCI integration configuration. 1. Review [Getting Started with Cloud SIEM](https://docs.datadoghq.com/getting_started/cloud_siem/) to configure threat detection. 1. Follow the [OCI configuration guide for Cloud SIEM](https://docs.datadoghq.com/security/cloud_siem/guide/oci-config-guide-for-cloud-siem/) to set up specific log sources and security rules for OCI. Cloud SIEM analyzes OCI logs to detect: - Unauthorized access attempts - Suspicious API calls - Configuration changes that may introduce security risks - Compliance violations ## Troubleshooting{% #troubleshooting %} If you encounter issues with the OCI integration, see the [OCI Integration Troubleshooting guide](https://docs.datadoghq.com/integrations/guide/oci-integration-troubleshooting). Need help? Contact [Datadog support](https://docs.datadoghq.com/help/). ## Further Reading{% #further-reading %} - [Monitor Oracle Cloud Infrastructure with Datadog](https://www.datadoghq.com/blog/monitor-oci-with-datadog/) - [Accelerate Oracle Cloud Infrastructure monitoring with Datadog OCI QuickStart](https://www.datadoghq.com/blog/datadog-oci-quickstart/) - [Oracle Cloud Infrastructure integration](https://docs.datadoghq.com/integrations/oracle-cloud-infrastructure) - [Why should I install the Datadog Agent on my cloud instances?](https://docs.datadoghq.com/agent/guide/why-should-i-install-the-agent-on-my-cloud-instances/)