Overview of Oracle Cloud Advisor
Cloud Advisor finds potential inefficiencies in your tenancy and offers guided solutions that explain how to address them. The recommendations help you maximize cost savings and improve the security of your tenancy. The built-in Cloud Guard recommendations help you see and address security vulnerabilities. You can also customize Cloud Advisor by postponing or dismissing recommendations that aren't applicable, allowing you to focus on the recommendations that matter most to you.
Cloud Advisor helps you:
- Downsize underutilized compute instances: Find and adjust underutilized compute instances to save money without degrading performance.
- Resize underutilized Autonomous Data Warehouse and Autonomous Transaction Processing databases: Your Autonomous Data Warehouse or Autonomous Transaction Processing databases might be provisioned for more CPUs than you are using. Reducing the number of CPUs allocated to your databases saves you money.
- Attach or delete orphaned block volumes and boot volumes: Cloud Advisor finds block volumes and boot volumes that are not being used by any compute instance so that you can attach or terminate them to reduce costs. Enable auto-tune to configure your block volumes and boot volumes to use the optimal performance setting based on whether the volume is attached or detached from an instance.
- Enable monitoring for compute instances: Monitoring compute instances allows Cloud Advisor to provide tailored recommendations.
- Enable object lifecycle management: You can define lifecycle policy rules that instruct Object Storage to automatically archive or delete resources within a given bucket based on criteria that you set.
- Stop idle compute instances: Cloud Advisor finds compute instances that you are no longer using and recommends that you stop them.
You can access the Cloud Advisor service to view, implement, postpone, or dismiss recommendations using the Console and the REST API.
The Cloud Advisor service is integrated with Oracle Cloud Infrastructure Identity and Access Management (IAM), which provides easy authentication with native Oracle Cloud Infrastructure identity functionality.
How Cloud Advisor Works
Cloud Advisor scans your tenancy once per day to identify specific cost-saving recommendations. After seven days, Cloud Advisor accumulates enough data to provide recommended actions with associated cost savings estimates. For Cloud Advisor to see CPU utilization and provide compute recommendations, you must allow monitoring of compute instances. When monitoring is not enabled, Cloud Advisor recommends that you enable it. For more information, see Enabling Monitoring for Compute Instances.
When Cloud Advisor has enough data to provide recommendations, a list of recommendations appears in the Recommendations dashboard. When applicable, the recommendations include cost savings estimates. In the Recommendations dashboard, you can implement, postpone, or dismiss the recommendations. For more information, see Customizing the Recommendation List.
Whenever possible, Cloud Advisor allows you to implement recommendations directly from the Recommendations dashboard. Often, you can implement the recommendation either for specific resources or for all resources in the tenancy that the recommendation applies to. When you implement a recommendation within Cloud Advisor, a work request for the change is created. When the work request completes, the new status appears in the History table. You can also implement the recommendations through the API or manually in the Console. In those cases, the new status is reflected in the History table the next time Cloud Advisor scans your tenancy.
How Cost Savings Estimates Are Calculated
Cloud Advisor estimates cost savings for most of its recommendations, providing a dollar amount representing an estimate of how much lower your costs could be if you implement the recommendation. This section lists each recommendation that comes with a cost savings estimate and describes how Cloud Advisor calculates that estimate.
For each recommendation, Cloud Advisor uses the data from the previous billing month when available. If the resource was created during the previous billing month and a full month's data is not yet available, Cloud Advisor underestimates cost savings until it has a full month's data. If the resource did not exist during the previous billing month, Cloud Advisor uses the current month's data, from the first day of the month to the current day. In that scenario, Cloud Advisor also underestimates cost savings until a full month's data is available.
- Downsize underutilized compute instances
For the resource that the recommendation applies to, Cloud Advisor subtracts the recommended OCPU from the current OCPU. It then multiplies the result by the billed usage and by the unit price. That value is divided by the current OCPU.
- Stop idle compute instances
For each compute instance, Cloud Advisor multiplies the billed usage by the unit price.
- Resize underutilized Autonomous Data Warehouse and Autonomous Transaction Processing databases
For the resource's compute costs, Cloud Advisor multiplies the billed usage by the unit price, and then divides that value in half.
- Attach or delete orphaned block volumes and boot volumes
Cloud Advisor estimates how much money would be saved by deleting the unattached block volume or boot volume. For the resource that the recommendation applies to, Cloud Advisor uses the billed usage for performance units and storage.
- Enable Object Lifecycle Management
For each Object Storage bucket, Cloud Advisor multiplies the billed usage by the unit price and then takes 45 percent of that value. Cloud Advisor uses 45 percent because overall customer trends indicate that over time, buckets with lifecycle management enabled trend toward a balance of 50 percent archive storage and 50 percent standard storage. Therefore, Cloud Advisor estimates that the current standard storage for a bucket will, over time, convert to a balance of 50 percent archive storage and 50 percent standard storage.
The actual ratio varies based on the bucket's purpose. Although Cloud Advisor estimates a 45 percent savings, the savings could be as high as 90 percent or as low as 0.
You can also use Object Lifecycle Management to:
- delete all objects in a bucket or objects that match the names filters that you specify, or
- delete uncommitted or failed multipart uploads.
Cloud Advisor does not provide cost savings estimates for these deletions.
Here's a list of basic concepts for Cloud Advisor.
- Cloud Advisor scans your tenancy to find potential inefficiencies and then uses this information to provide recommendations that suggest ways to reduce costs and increase efficiency. For information about the specific types of recommendations, see Implementing Cloud Advisor Recommendations.
- Estimated cost savings
- Cloud Advisor provides estimated cost savings for applicable recommendations. This value is a dollar amount estimating how much lower your costs could be if you implement the recommendation. These values are estimates and are not guaranteed. For more information, see How Cost Savings Estimates Are Calculated.
- Each recommendation has a status that reflects its current state.
- When Cloud Advisor identifies a recommendation but no user action has been taken, the recommendation is Pending. Cloud Advisor evaluates each resource once every 24 hours.
- When a recommendation is Implemented, Cloud Advisor has made the recommendation, and the suggested change has been made in the tenancy. The recommendation status is also Implemented when a recommendation is no longer applicable because of a change in usage in your tenancy.
- When a recommendation is Postponed, it does not appear in your dashboard until a future date that you choose.
- When a recommendation is Dismissed, it does not appear in your dashboard until you reactivate it.
- A recommendation is Reactivated when the recommendation was previously postponed or dismissed but has been reinstated.
- You can implement a recommendation to make the suggested change to your resources.
- When you use the Cloud Advisor interface to implement a recommendation, a work request is created. When the work request completes, a row appears in the History table with the recommendation status Implemented.
- When you implement a recommendation using a work flow outside of Cloud Advisor, an entry appears in the History table after Cloud Advisor scans the tenancy.
- You can postpone a recommendation so that it does not appear in your
dashboard until a future date of your choice.
- When you postpone a recommendation for a single resource or for a select list of resources, a row for each resource appears in the History table. The recommendation status is Postponed.
- When you postpone a recommendation for all resources, no entry appears in the History table, and no existing recommendations become postponed. Postponing a recommendation for all resources prevents Cloud Advisor from making new recommendations of this type until the postponement expires.
- You can dismiss a recommendation so that it no longer appears in your dashboard.
- When you dismiss a recommendation for a single resource or for a select list of resources, a row for each resource appears in the History table. The recommendation status is Dismissed.
- When you dismiss a recommendation for all resources, no entry appears in the History table, and no existing recommendations become dismissed. Dismissing a recommendation for all resources prevents Cloud Advisor from making new recommendations of this type unless the recommendation is reactivated.
- You can reactivate a recommendation that has been postponed or dismissed,
and Cloud Advisor once again includes this
recommendation when it scans your tenancy. The status temporarily changes to
Pending, and the next time Cloud Advisor scans the tenancy, Cloud Advisor updates the recommendation status
and the associated cost savings estimate.
- When you reactivate a recommendation for a single resource or for a select list of resources, a row for each resource appears in the History table. The recommendation status is Pending.
- When you reactivate a recommendation for all resources, no entry appears in the History table.
Ways to Access Oracle Cloud Infrastructure
You can access Oracle Cloud Infrastructure using the Console (a browser-based interface) or the REST API. Instructions for the Console and API are included in topics throughout this guide. For a list of available SDKs, see Software Development Kits and Command Line Interface.
To access the Console, you must use a supported browser. To go to the Console sign-in page, open the navigation menu at the top of this page and click Infrastructure Console. You will be prompted to enter your cloud tenant, your user name, and your password.
For general information about using the API, see REST APIs.
Most types of Oracle Cloud Infrastructure resources have a unique, Oracle-assigned identifier called an Oracle Cloud ID (OCID). For information about the OCID format and other ways to identify your resources, see Resource Identifiers.
Authentication and Authorization
Each service in Oracle Cloud Infrastructure integrates with IAM for authentication and authorization, for all interfaces (the Console, SDK or CLI, and REST API).
An administrator in your organization needs to set up groups , compartments , and policies that control which users can access which services, which resources, and the type of access. For example, the policies control who can create new users, create and manage the cloud network, launch instances, create buckets, download objects, etc. For more information, see Getting Started with Policies. For specific details about writing policies for each of the different services, see Policy Reference.
If you’re a regular user (not an administrator) who needs to use the Oracle Cloud Infrastructure resources that your company owns, contact your administrator to set up a user ID for you. The administrator can confirm which compartment or compartments you should be using.