CloudOCI Service Connector Hub + Terraform

Oracle Cloud (OCI) Integration

Monitor compute, networking, and Autonomous Database metrics across your Oracle Cloud Infrastructure. Correlate OCI resource health with application performance for complete observability of your OCI workloads.

Connect OCI Book a Demo

Setup

How It Works

Configure OCI IAM Policy

Create a TigerOps OCI user or use instance principal authentication. Attach an IAM policy granting read access to OCI Monitoring, Compute, Networking, and Database services. The TigerOps setup wizard generates the exact policy statement.

Deploy the OCI Metrics Connector

Use the provided OCI Resource Manager stack or Terraform module to deploy the TigerOps OCI Metrics Connector. It creates an OCI Service Connector Hub that streams metrics from OCI Monitoring to TigerOps in near real-time.

Select Metric Namespaces

Choose the OCI metric namespaces to collect: oci_computeagent for VM metrics, oci_lbaas for load balancer health, oci_autonomous_database for ADB metrics, oci_vcn for networking, and more. All are enabled by default.

Set Thresholds and Correlate Services

Define per-compartment and per-resource alert thresholds. TigerOps correlates OCI infrastructure metrics with your application traces and logs — linking VM CPU spikes with database query latency for complete incident context.

Capabilities

What You Get Out of the Box

Compute Instance Monitoring

Track OCI Compute instance CPU utilization, memory usage (via OCI Compute Agent), disk IOPS, and network throughput. Alert on consistently over-utilized shapes and identify right-sizing opportunities.

Autonomous Database Metrics

Monitor OCI Autonomous Database CPU utilization, storage consumption, SQL execution counts, and connection pool usage. Alert before ADB auto-scaling triggers unexpectedly and drives up costs.

Load Balancer & API Gateway Health

Track OCI Load Balancer backend health check statuses, active connection counts, and request rates. Monitor OCI API Gateway request metrics and 4xx/5xx error rates per API deployment.

VCN & Networking Metrics

Monitor VCN subnet ingress/egress bytes, VPN IPSec tunnel health, FastConnect circuit bandwidth utilization, and NAT gateway packet rates for complete OCI networking visibility.

Object Storage & Block Volume Health

Track OCI Object Storage request rates and error rates, Block Volume IOPS utilization against provisioned capacity, and Ultra High Performance volume queue depths.

AI Root Cause Analysis

When OCI workloads degrade, TigerOps AI correlates compute resource saturation, Autonomous Database performance events, network packet loss, and application error traces to identify the root cause across the entire OCI stack.

Configuration

OCI Terraform Module Deployment

Deploy the TigerOps OCI Service Connector Hub using the Terraform module in your OCI tenancy.

main.tf

# TigerOps OCI Metrics Connector — Terraform module
module "tigerops_oci" {
  source  = "tigerops/oci-connector/oracle"
  version = "~> 1.0"

  # OCI tenancy and compartment
  tenancy_ocid     = var.tenancy_ocid
  compartment_ocid = var.compartment_ocid
  region           = "us-ashburn-1"

  # TigerOps endpoint and API key
  tigerops_endpoint = "https://ingest.atatus.net/oci/v1/stream"
  tigerops_api_key  = var.tigerops_api_key

  # OCI metric namespaces to stream
  metric_namespaces = [
    "oci_computeagent",           # VM CPU, memory, disk, network
    "oci_autonomous_database",    # ADB CPU, storage, SQL counts
    "oci_lbaas",                  # Load Balancer health
    "oci_vcn",                    # VCN subnet traffic
    "oci_objectstorage",          # Object Storage requests
    "oci_blockstore",             # Block Volume IOPS
    "oci_apigateway",             # API Gateway request metrics
  ]

  # Alert thresholds (applied as OCI Alarm rules)
  alerts = {
    compute_cpu_warning_pct  = 80
    compute_cpu_critical_pct = 95
    adb_cpu_warning_pct      = 70
    adb_storage_warning_pct  = 80
    lb_unhealthy_backends     = 1
  }
}

output "service_connector_ocid" {
  value = module.tigerops_oci.service_connector_ocid
}

FAQ

Common Questions

How does TigerOps collect metrics from Oracle Cloud Infrastructure?

TigerOps uses the OCI Service Connector Hub to stream metrics from OCI Monitoring to a TigerOps HTTP endpoint. This is the most efficient approach — metrics are pushed in near real-time rather than polled, and the Service Connector handles retry and ordering guarantees.

What OCI IAM permissions does TigerOps require?

TigerOps requires read-only access to OCI Monitoring (METRIC_QUERY_INSPECT, METRIC_QUERY_READ), Compute (INSTANCE_INSPECT), Load Balancer (LOAD_BALANCER_INSPECT), and Autonomous Database (AUTONOMOUS_DATABASE_INSPECT) policies. The setup wizard generates the exact policy statement for your tenancy.

Can TigerOps monitor OCI resources across multiple compartments?

Yes. Configure TigerOps with compartment OCIDs or grant tenancy-root access to monitor all compartments. Resources are labeled with their compartment path so you can filter dashboards and alerts by compartment hierarchy.

Does TigerOps support OCI Autonomous Database Serverless monitoring?

Yes. For ADB Serverless instances, TigerOps monitors the oci_autonomous_database metrics namespace including CPU utilization, storage used, running SQL count, queued SQL count, and ECPU consumption — all critical for managing ADB Serverless costs and performance.

Can TigerOps monitor OCI Container Instances and OKE clusters?

Yes. OCI Container Instance CPU and memory metrics are collected from the oci_containerinstances namespace. For OKE (Oracle Kubernetes Engine) clusters, TigerOps collects node-level OCI metrics plus Kubernetes API server metrics via the standard TigerOps Kubernetes integration.

Get Started

Stop Discovering OCI Infrastructure Issues After Autonomous Database Auto-Scales

Compute health alerts, ADB performance monitoring, and cross-service correlation. Deploy via Terraform in minutes.

Start Free Talk to an Engineer