Cloud Advisor Overview
Cloud Advisor finds potential inefficiencies in your tenancy and offers guided solutions to help you address them.
Cloud Advisor helps you:
- Save money: Cost management recommendations find underutilized resources so that you can save money without degrading performance.
- Improve performance: Performance recommendations find overutilized resources, recommend adjustments, and identify block volumes and boot volumes that aren't using the performance auto-tuning feature.
- Strengthen system resilience: High availability recommendations provide hardware failure best practices to ensure the resilience and business continuity of your environment.
- Improve security: The built-in Cloud Guard recommendations help you see and address security vulnerabilities.
Cloud Advisor has three recommendation categories:
You can access the Cloud Advisor service to view, implement, postpone, or dismiss recommendations using the Console, REST API, and CLI. To customize Cloud Advisor, postpone or dismiss recommendations that aren't applicable to you, and choose the recommendation profiles that best match your needs.
With Cloud Advisor, you can view a consolidated graphical display that shows a summary of recommendations to improve cost savings and performance. You can use to create an adequate budget for the tenancy's operation. You can also view the high availability recommendations by region and tenancy to find tenancies and departments that have a high risk of infrastructure failure. With that information, you can then set rules or guidelines to enforce best practices to avoid creating resources in certain regions.
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.
Cloud Advisor makes cross-region calls to consolidate usage data and resource metadata from all regions subscribed to the tenancy. Cloud Advisor stores this data in the tenancy's home region to aggregate the data and generate recommendations.
How Cloud Advisor Works
Cloud Advisor scans your tenancy once per day to identify recommendations. Depending on the recommendation type, Cloud Advisor either provides recommendations immediately after scanning the tenancy, or after seven days, when Cloud Advisor has accumulated enough data to recommend actions. 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.
Cloud Advisor makes cross-region calls to consolidate usage data and resource metadata from all regions subscribed to the tenancy. Cloud Advisor stores this data in the tenacy's home region to aggregate the data and generate recommendations.
When Cloud Advisor has enough data to provide recommendations, it displays a list of recommendations 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 Implementing Cloud Advisor Recommendations.
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. 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.
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 are 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.