Monitor Oracle Cloud Infrastructure (OCI) Compute Instances using read-only API key credentials. Cloudmon auto-discovers your instances and begins collecting metrics in real time.
OCI (Oracle Cloud Infrastructure) Compute Instances are virtual machines running in Oracle's cloud. Cloudmon connects to OCI using an API key associated with a user in your OCI tenancy, then discovers and monitors Compute Instances on a recurring schedule.
Navigate to Cloud → OCI → [Your OCI Account] to view the account overview. The page shows a breakdown of all discovered resources by type, a geographical and regional breakdown of resources, and three action buttons in the top right: Rediscover, Edit, and Delete.
To connect an OCI account for the first time, including how to generate the required API key in the OCI console, refer to How to Set Up OCI Monitoring in Cloudmon.
The account overview page at Cloud → OCI → [Your OCI Account] shows a donut chart of resources by type, an OCI Compute Instance count tile, a Resources Breakdown tree listing each discovered instance with a live status indicator, and a Geographical View map switchable between Geographical and Heatmap views, alongside a By Regions breakdown table.
From the OCI Compute Instance list, click an instance's edit icon to open a quick Edit panel with two sections: Configuration Details (Groups, Depends on, Tags) and Alert Settings (Alarm Rule, User Groups, Third Party Services). This is the same Groups, Depends On, and Alarm Rule pattern used for individual resources across other Cloudmon Cloud monitors. Click Save to apply changes.
Clicking into an OCI Compute Instance opens its detail page, organized into five tabs: Overview, Networking, Storage, System Metrics, and Outages, plus an Alarms tab.
| Tab | What it shows |
| Overview | Availability, downtime, vCPU and memory usage gauges, current operating system, and any active alarms. The side panel shows the instance's shape, private and public IP, groups, status, monitoring state, and last polled time. General Information covers the Instance OCID, availability domain, fault domain, launch mode, lifecycle state, compartment, region, and creation details. Image Information, Shape Configuration, and Launch Options panels show the instance's image, vCPU and memory allocation, network bandwidth, processor, firmware, and security-related settings such as Encryption in transit and Legacy IMDS. An Agent Plugins panel lists every OCI management agent plugin available for the instance and flags which ones are currently enabled. |
| Networking | Network interface and connectivity details for the instance. |
| Storage | Boot and block volume details attached to the instance. |
| System Metrics | Time-series charts for performance metrics collected from the instance. |
| Outages | A history of availability outages recorded for the instance. |
| Alarms | Alarm triggers and history for the instance. |
If device monitoring is disabled for an instance, a red banner appears at the top of the Overview tab stating that device monitoring is disabled, and the instance's State shows as Not Monitored. Monitoring is enabled or disabled using the toggle in the OCI Compute Instance list, or from the instance's own edit panel.
Each alarm is built around a simple IF/THEN model, where you select a metric, set a threshold, and define what happens when it is breached. To attach an alarm rule to an instance, open its quick Edit panel and select the desired profile from the Alarm Rule field under Alert Settings. The User Groups and Third Party Services assigned in the same section are inherited automatically by the attached alarm rule.
| Symptom | Likely Cause | Fix |
| Instance shows "Device monitoring disabled" and State as Not Monitored | Monitoring was turned off for this instance, either manually or because it was deleted in OCI and Monitor terminated resources was not enabled | Re-enable the toggle for the instance in the OCI Compute Instance list if it should still be monitored |
| A previously visible instance disappeared from the list | The instance was terminated in OCI and Automatically Remove Terminated Resources is enabled, so it was removed after the configured retention period | If terminated instances should remain visible, edit the account and enable Monitor terminated resources, or disable Automatically Remove Terminated Resources |
| Alarms not triggering as expected | Alarm thresholds may not be configured for this instance | Open the instance's quick Edit panel and confirm an Alarm Rule is selected under Alert Settings |
| New OCI resources not appearing in an existing account | Enable auto-discovery is off, or the Rediscovery Interval has not elapsed yet | Navigate to Cloud → OCI → [Account] and click Rediscover to trigger a manual scan, or edit the account to enable auto-discovery |
| No resources discovered for a newly added account | A credential or configuration issue during account setup | Refer to the Troubleshooting section in How to Set Up OCI Monitoring in Cloudmon |