Skip to main content

Prerequisites

  • An Oracle Cloud Infrastructure (OCI) account
  • Permission to create users, API keys, and manage log groups in your OCI tenancy
  • The following OCI identifiers:
    • Tenancy OCID
    • User OCID
    • Compartment OCID

Step-by-Step Setup

1. Navigate to Integrations

In your Corelayer dashboard, go to the Integrations page.

2. Add OCI Integration

Click the Add Integration button and select Oracle Cloud (OCI) from the list of available integrations.

3. Create an API Signing Key

In your OCI console:
  1. Navigate to Identity > Users > Your User > API Keys
  2. Click Add API Key
  3. Generate or upload a key pair
  4. Copy the Fingerprint of the key
  5. Download or copy the Private Key (PEM)

4. Enter Credentials

Provide the following details:
  • Tenancy OCID — Your OCI tenancy identifier (e.g., ocid1.tenancy.oc1..xxxx)
  • User OCID — The OCI user identifier (e.g., ocid1.user.oc1..xxxx)
  • Fingerprint — The API key fingerprint
  • Private Key (PEM) — The private key contents
  • Region — Your OCI region (e.g., us-ashburn-1)
  • Compartment OCID — The compartment to monitor (e.g., ocid1.compartment.oc1..xxxx)

5. Test Connection

Click Test Connection to verify that Corelayer can authenticate with your OCI tenancy.

6. Select Log Groups

Once connected, select which OCI log groups you want Corelayer to monitor:
  • Browse the list of available log groups in your compartment
  • Check the boxes next to the log groups you want to include
  • Click Update Selection

7. Add OCI Log Groups to Your Service Maps

When configuring your Corelayer Service Maps, select which OCI log groups are relevant to each service.

What Corelayer Can Do With OCI

Once connected, Corelayer will:
  • Monitor selected log groups for errors and anomalies
  • Query OCI logs to gather context during debugging
  • Correlate OCI log data with other integrations for root-cause analysis

Managing Your Integration

Disconnecting

To disconnect your OCI integration:
  1. Navigate to Settings > Integrations
  2. Find your OCI integration and click Uninstall
  3. Confirm the uninstallation
  4. Optionally, delete the API signing key from your OCI user settings

Troubleshooting

Integration Not Working?

  • Verify all OCIDs (tenancy, user, compartment) are correct and properly formatted
  • Ensure the API signing key fingerprint matches the key uploaded in OCI
  • Check that the private key PEM is complete and properly formatted
  • Confirm the specified region matches your OCI resources
  • Verify the user has the necessary IAM policies to read log groups
Need help? Contact support for assistance with your OCI integration.