Oracle Cloud Infrastructure Documentation

Set Up Resource Analytics

Resource Analytics provides a guided walkthrough to help you create a Resource Analytics instance. Visit the OCI Resource Analytics Console Overview page (OC1 realm) for more information and to create your instance.

  • To set up a Resource Analytics instance using the guided walkthrough, review the next section, Before You Begin, but skip the rest of this topic and chapter. Instead, see Creating an Instance.
  • To set up a Resource Analytics instance manually, review the setup procedures in the rest of this topic and complete the setup steps documented in this chapter.

Before You Begin

Before you create a Resource Analytics instance, refer to these topics to learn more about Autonomous AI Database and Oracle Analytics Cloud.

  1. Review some important aspects of using Autonomous AI Database with Resource Analytics.

    See Oracle Autonomous AI Database Considerations.

  2. Read about how to enable Oracle Analytics Cloud (OAC).

    See Oracle Analytics Cloud Considerations.

Required Prerequisites

If you want to manually create a Resource Analytics instance, you must review the required prerequisites, and then prepare both the tenancy where you want to provision it and any other tenancies whose resources you plan to monitor.

Confirm that your tenancy:

  • Has enough quota for one extra Oracle Autonomous AI Database (ADW).
  • Has subscriptions to all the regions your instance will monitor.

    See Managing Regions.

  • Has a compartment (not your tenancy's root compartment) where you'll create the Resource Analytics instance.

    See Select or Create a Compartment.

To use OAC for visualizations, your tenancy must:
  • Be enabled for identity domains.
  • Have an identity domain whose home is the same region as the Resource Analytics instance you're creating.
  • Have enough quota for one more OAC instance.

Required Setup

The following steps are required to manually provision a tenancy for Resource Analytics.

  1. Create a VCN with a private subnet with DNS enabled, plus security list rules letting ingress and egress on two ports.

    See Set Up Networking.

  2. Create policies to let administrative users manage Resource Analytics and to allow the service to access your resource metadata.

    See Create Groups, Dynamic Groups, and Policies and Create Policies for Remote Monitored Tenancies.