Overview
OCI Control Center (OCC) enables you to monitor region-level cloud consumption and provides region-level capacity data in realms where OCC is available. Use OCC to check the availability of resources and create and monitor capacity requests.
OCC includes the following features:
- Metrics monitoring: Use this feature in OCC to monitor region-level cloud consumption. Currently, metrics monitoring is available only to the owner or operator of the realm and is available in regions other than OC1. For example, for Compute, you can use the feature to view the number of used CPU cores and the number of available CPU cores. Similar data is available for services such as Object Storage, Block Storage, File Storage Service, and Exadata. Using this Console plugin, you can monitor the capacity consumption for all the regions of your realm.
Metrics Monitoring feature is available only to the owner or operator of the realm.
- Capacity Requests: Use this feature to check the availability of certain resources, create new capacity requests, or track the existing capacity request. For example, for Compute, you can use the information in the compute availability catalog to create the capacity request. The compute availability catalog lists the server availability in a certain region. This feature is available only in OC1.
The owner or operator of the OC1 realm is Oracle. There are other owner and operators for DRCC realms.
Key Capabilities
The key capabilities of OCC are as follows:
- Metrics Monitoring: Monitor region-level cloud consumption and capacity. OCC enables you to export data for further analysis and reporting. You can also read the metrics as JSON data using API.
- Capacity Management: Request for additional physical resources in OC1. You can perform the following tasks from the Console and SDKs/CLI:
- List and export the latest version of availability catalogs
- Create new capacity requests
- Track lifecycle of capacity requests
Accessing OCC
To access the Console, you must use one of the following supported browsers:
- Google Chrome 69 or later (preferred browser)
- Firefox 62 or later
- Safari 12.1 or later
When you sign in to the Console, you're prompted to enter your cloud tenant, your user name, and your password.
For information, see supported browsers and security credentials.
Avoid entering confidential information when assigning descriptions, tags, or friendly names to your cloud resources through the Console, API or CLI.
If you perform an action and get a message that you don't have permission or are unauthorized, then confirm with your administrator the type of access you have.
- To use the CLI or REST APIs in Cloud Shell, sign in to the Console. See Using Cloud Shell and the CLI Command Reference.
- To install the OCI CLI in your environment, follow the steps in the Install CLI quick start. For a list of available SDKs, see SDKs and the CLI. Also, see Command Line Interface (CLI).
- When using REST APIs, see the REST API documentation and API Reference and Endpoints.
While performing an action, if you get any issues related to permission or authorization, then contact your administrator to check the type of access.
To get started with the OCC, see Getting Started with OCC.
Authentication and Authorization
Each service in OCI integrates with IAM for authentication and authorization for all interfaces (the Console, SDK or CLI, and REST API).
An administrator in your company needs to set up groups, compartments , and policies that control who can access different services and resources (metric data), and the type of their access.
- If you're a new administrator, see Getting Started with Policies.
- For details about writing policies for OCI Control Center, see OCC Policies and Permissions.
- For details about writing policies for other services, see Policy Reference.
If you're a regular user (not an administrator) who needs to use OCC, contact your administrator to set up a user ID for you.
Resources in OCC
- Metrics Monitoring:
OCC doesn't generate any OCI resources. However, OCC provides access to region-level metric data. The metric data in OCC is contained in the service and isn't associated with any OCI resource or a specific compartment.
However, you must specify a compartment (typically, the root compartment) to access the data. The permissions model allows the administrators to restrict access to the metric data based on users, groups, or both users and groups. For details, see OCC Policies and Permissions.
- Capacity Management: Use the following OCC resources to manage data.
-
Availability Catalogs: It displays the current availability of resources for a specific namespace.
-
Capacity Requests: It is a request to reserve a part of the available capacity for use. A capacity request resource contains a list of quantities of specific server shapes, in a specific location and capacity handover date.
-
Resource Identifiers
The metrics monitoring feature in OCC doesn't generate any OCI resources. However, OCC provides access to region-level metric data. The metric data in OCC is contained in the service and isn't associated with any OCI resource or a specific compartment.
Resources for capacity management, similar to most types of resources in OCI, have an Oracle Cloud ID (OCID), which is an Oracle-assigned unique identifier.
For information about the OCID format and other ways to identify your resources, see Resource Identifiers.
You must specify a compartment (typically, the root compartment) to access the data. The permissions model allows the administrators to restrict access to the metric data based on users, groups, or both users and groups. It also restricts access to CRUD operations on the capacity management resources. For details, see OCC Policies and Permissions.
Regions and Availability Domains
-
Metrics monitoring in OCC is currently available in Dedicated Region Cloud@Customer (DRCC) and Alloy realms and in all the regions within the realms.
-
Capacity Requests is available in all Oracle Cloud Infrastructure commercial regions. However, it is available only for large customers.