Skip to content

oci.md

Latest commit

 

History

History
236 lines (153 loc) · 13.3 KB

oci.md

File metadata and controls

236 lines (153 loc) · 13.3 KB
title description further_reading
Getting Started with Oracle Cloud Infrastructure (OCI)
Integrate your Oracle Cloud Infrastructure environment with Datadog for comprehensive monitoring
link tag text
Blog
Monitor Oracle Cloud Infrastructure with Datadog
link tag text
Blog
Accelerate Oracle Cloud Infrastructure monitoring with Datadog OCI QuickStart
link tag text
/integrations/oracle-cloud-infrastructure
Documentation
Oracle Cloud Infrastructure integration
link tag text
/agent/guide/why-should-i-install-the-agent-on-my-cloud-instances/
Guide
Why should I install the Datadog Agent on my cloud instances?

{{< jqmath-vanilla >}}

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.

{{% collapse-content title="Prerequisites" level="h4" expanded=false id="prerequisites" %}}

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

A Datadog account with permissions to create API and application keys.

{{% /collapse-content %}}

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 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

  1. Go to the Datadog OCI integration tile and click Add New Tenancy.

  2. Select or create a Datadog API key to use for the integration.

  3. Create a Datadog application key.

  4. Enable or disable logs using the toggle.

  5. 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

  1. In the OCI console, accept the Oracle Terms of Use.

  2. Leave the option to use custom Terraform providers unchecked.

  3. Use the default working directory, or optionally choose a different one.

  4. Click Next.

  5. 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.

  6. 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.

  7. 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.

  8. Click Next.

  9. Click Create, and wait up to 30 minutes for the deployment to complete.

Complete the setup in Datadog

Return to the Datadog OCI integration tile and click Ready!

Validation

Wait up to 10 minutes for data to start being collected, and then view oci.* metrics in the OCI integration overview dashboard or Metrics Explorer page in Datadog.

{{< img src="getting_started/integrations/oci/oci-dashboard.png" alt="The OCI overview dashboard in Datadog with various metrics and graphs from Oracle Cloud Infrastructure services">}}

OCI function metrics (oci.faas namespace) and container instance metrics (oci_computecontainerinstance namespace) are in Preview.

Configuration

After completing the setup, a configuration tab for the tenancy becomes available on the left side of the Datadog OCI integration tile. Apply tenancy-wide data collection configurations as outlined below.

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

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

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

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.

{{% collapse-content title="Tag filter syntax" level="h5" id="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.

{{% /collapse-content %}}

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

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

On the Resource Collection tab of the Datadog OCI integration tile, click the Enable Resource Collection toggle. Resources are visible in the Datadog Resource Catalog.

Get more from the Datadog platform

Install the Agent for deeper visibility

While the OCI integration automatically collects service-level metrics through Oracle Cloud Monitoring, installing the Datadog 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
  • 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 for instructions, or read why you should install the Agent on cloud instances for more details on the benefits.

Use the Datadog Agent with OCI Kubernetes Engine (OKE)

For containerized environments on OKE, you can use the Datadog Agent for Kubernetes. 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

GPU monitoring

Monitoring OCI GPU instances is essential for ensuring optimal performance and reliability of your high-performance computing workloads. The OCI GPU integration 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.

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 (created automatically when you set up the OCI GPU integration) for an overview of your GPU infrastructure.

Cloud Cost Management

Datadog's Oracle Cloud Cost Management 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.
  2. Follow the setup instructions in the Oracle Cloud Cost Management documentation to enable cost data collection.

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.
  2. Review Getting Started with Cloud SIEM to configure threat detection.
  3. Follow the OCI configuration 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

If you encounter issues with the OCI integration, see the OCI Integration Troubleshooting guide.

Need help? Contact Datadog support.

Further Reading

{{< partial name="whats-next/whats-next.html" >}}