Connect your Oracle Cloud Infrastructure (OCI) account to Cloudmon using a read-only API key. Once connected, Cloudmon auto-discovers your Compute Instances and begins collecting metrics in real time.
Oracle Cloud Infrastructure (OCI) is Oracle's cloud platform, providing hosted compute, storage, networking, and database services over the internet. Organisations use OCI to run workloads without managing physical hardware, with resources deployed across Oracle's global network of data centres.</p> <p>This guide walks you through connecting your OCI account to Cloudmon for the first time. The setup involves generating an API key for a user in the OCI console, followed by entering that user's credentials into Cloudmon. Once complete, Cloudmon will have read-only access to your OCI tenancy and will automatically discover your Compute Instances.
Before you begin, ensure the following are in place:
| Requirement | Description |
| OCI account access | You must be able to sign in to the OCI console as the user whose API key will be used, or have an administrator generate one for you |
| Cloudmon account | An active Cloudmon account with Cloud Monitoring enabled |
| Compartment access | Know the OCID of the compartment containing the Compute Instances you want to monitor |
Cloudmon connects to your OCI tenancy using an API key associated with a specific OCI user. This key is used to authenticate read-only API calls to OCI on a recurring schedule, pulling Compute Instance metrics, resource lists, and configuration data. Nothing is installed inside your OCI environment, and no Cloudmon probe is required: the connection is made directly from the Cloudmon Controller using the credentials you provide.
Decide which OCI user's API key Cloudmon will use, and which compartment holds the Compute Instances to be monitored. Note down the following from the OCI console, you will need these in Step 3:
Follow the Oracle documentation to generate an API signing key pair for the user identified in Step 1 and upload the public key in the OCI console: How to Generate an API Signing Key, Oracle documentation
Once the key is added, note down the following, you will need these in Step 3:

Important: The private key file is only available to download at the time it is generated. Store it securely; you will need to upload it into Cloudmon in Step 3.
Monitor Details: basic details and connection credentials.
| Field | Description |
| Display Name* | A friendly name for this OCI account, e.g. "OCI Production" |
| Region* | The OCI region this account's resources are deployed in |
| Compartment ID* | The Compartment OCID identified in Step 1 |
| User OCID* | The User OCID identified in Step 1 |
| Fingerprint* | The fingerprint generated in Step 2 |
| Private key file (.pem)* | Click Choose PEM file and upload the private key file downloaded in Step 2 |
Discovery Settings: services and discovery settings.
| Field | Description |
| Services to be discovered* | OCI Compute Instance is currently the only supported service |
| Enable auto-discovery | Enabled by default. Automatically discovers OCI VM resources on a recurring schedule |
| Rediscovery Interval | How frequently Cloudmon re-scans the account for new or removed resources. Defaults to 6 Hours |
| Notify on Discovery | Toggle on to receive a notification once new resources are discovered |
Resource Management: monitoring options.
| Field | Description |
| Mute Resource Termination Alerts | Toggle on to stop triggering alerts when a resource is deleted in OCI |
| Monitor terminated resources | Toggle on to keep terminated resources visible in monitoring |
| Automatically Remove Terminated Resources | Enabled by default. Auto-deletes terminated VM monitors after the configured retention period |
| Remove Terminated Resources After* | How long a terminated resource's monitor is retained before removal. Defaults to 7 Days. Only visible when automatic removal is enabled |
| Include/Exclude Resources based on Tags | Choose whether OCI tags exclude matching resources from discovery or include only matching resources |
Configuration Details: groups and tags.
| Field | Description |
| Groups | Optional groups to organise this account alongside others |
| Tags | Optional tags to associate with this OCI account |
Alert Settings: notification and alert configuration.
| Field | Description |
| User Groups | The user groups to notify when an alert is raised on any resource discovered under this account |
| Third Party Services | Third-party integrations to use for alert notifications on resources discovered under this account |
After saving, navigate to Cloud → OCI → [Your Account]. If the connection is successful, your discovered OCI Compute Instances will begin populating within a few minutes. If resources do not appear, use the Rediscover button on the account page to trigger a manual scan.
| Issue | Likely Cause | Resolution |
| No resources discovered after saving | Incorrect Compartment ID, User OCID, Fingerprint, or private key, or the API key is not registered for that user in OCI | Re-check the credentials in the OCI console under the user's API Keys, and confirm the Region and Compartment ID are correct |
| Authentication error on save | The Fingerprint does not match the uploaded private key, or the private key file is corrupted | Re-generate the API key pair in OCI and re-upload the matching Fingerprint and private key in Cloudmon |
| Compute Instances in the compartment are not appearing | Wrong Compartment ID, or the instances are in a different region than the one configured | Confirm the Compartment OCID and Region match where the instances are actually deployed in the OCI console |
| Resources not updating | Enable auto-discovery is off, or the Rediscovery Interval has not elapsed yet | Navigate to Cloud → OCI → [Account] and click Rediscover, or edit the account to enable auto-discovery |