OCI OKE Monitoring in ObserveOps
ObserveOps (formerly known as AIOps) supports monitoring of Oracle Container Engine for Kubernetes (OCI OKE). Use this integration to track the health and performance of your OKE clusters, node pools, and workloads from a single ObserveOps monitoring view.
Prerequisites
- An active OCI account with at least one OKE cluster running.
- An OCI user with IAM permissions to read OKE cluster metrics (policy:
inspect cluster-family). - OCI API keys or Instance Principal authentication configured for ObserveOps.
- The ObserveOps collector has outbound HTTPS access to the OCI API endpoint for your region.
How It Works
ObserveOps connects to the OCI API using the credentials you configure in the OCI credential profile. It queries OKE cluster metadata and node pool status at your configured polling interval. The collected data populates the OCI OKE monitor tabs in ObserveOps, and metrics feed into alerts, dashboards, and topology views.
Add an OCI Credential Profile
Before discovering OCI OKE, add an OCI credential profile with the required API keys:
- Go to Settings, then select Credential Profile.
- Click Create Credential Profile and select OCI.
- Fill in the OCI credential fields:
| Field | Description |
|---|---|
| Profile Name | A unique name for this credential — e.g., OCI-Production. |
| Tenancy OCID | The OCID of your OCI tenancy. Find it in OCI Console → Profile → Tenancy. |
| User OCID | The OCID of the OCI user ObserveOps uses for API calls. |
| Region | The OCI region — e.g., ap-mumbai-1, us-ashburn-1. |
| Fingerprint | The fingerprint of the API key uploaded to the OCI user. |
| Private Key | Paste the contents of the private key (.pem) file associated with the fingerprint. |
- Click Save.
Discover OCI OKE Clusters
- Go to Menu and select Settings.
- Select Discovery, then select Cloud Discovery Profile.
- Click Create Cloud Discovery Profile.
- Select Oracle Cloud as the cloud provider.
- Select OCI OKE as the service type.
- Select the OCI credential profile you created.
- Configure Group, Tags, and Collector.
- Click Save, then click Discover Now.
ObserveOps discovers all OKE clusters accessible with the configured credentials and adds them as monitors.
Available Monitoring Views
The OCI OKE monitor provides the following tabs:
| Tab | What It Shows |
|---|---|
| Overview | Cluster status, Kubernetes version, VCN, endpoint visibility, cluster age, total node pools, total nodes |
| Node Pool | Node pool name, state, node shape, Kubernetes version, node count, subnet, fault domains |
Example
A DevOps team runs three OKE clusters across two OCI regions for development, staging, and production. They add OCI credential profiles for each region and create a Cloud Discovery Profile for OCI OKE. ObserveOps discovers all three clusters and starts monitoring node pool health. When a production node pool drops below the minimum healthy node count, an ObserveOps alert fires before the on-call engineer's monitoring script detects the issue.
Troubleshooting
OCI OKE clusters do not appear after discovery
Cause: The OCI user lacks the IAM policy to inspect OKE resources, or the tenancy OCID is incorrect.
Fix: In OCI Console, add the policy Allow group <group-name> to inspect cluster-family in tenancy and verify the tenancy OCID in the credential profile.
Discovery fails with "authentication error"
Cause: The private key or fingerprint does not match the API key configured for the OCI user. Fix: In OCI Console, go to the user's API Keys section, delete and re-add the key, and update the credential profile with the new fingerprint and private key.
Node pool shows 0 nodes after discovery
Cause: Node pools are being created or the cluster is in a transitional state. Fix: Wait for the cluster to reach Active state in OCI Console, then trigger Re-discover from the monitor's action menu.
Known Limitations
- ObserveOps monitors OCI OKE at the cluster and node pool level. Pod-level and container-level metrics require Kubernetes metrics integration via MotaAgent deployed inside the cluster.
- OKE clusters using private endpoints require the ObserveOps collector to be deployed inside the same VCN or via a connected network.