Customizing Cloud Advisor Recommendations

You can customize Cloud Advisor by postponing or dismissing recommendations and by customizing the logic that Cloud Advisor uses to make recommendations. Modify the recommendations based on your preferences and what works best for your workloads.

Cloud Advisor provides recommendations to help you maximize cost savings and improve the performance, security, and availability of your tenancy. However, you might want to customize recommendations for certain resources, postpone specific recommendations to review later, or dismiss recommendations entirely. Recommendation overrides and changes to recommendation overrides take effect the next time Cloud Advisor runs for your tenancy.

Required IAM Policies

To use Oracle Cloud Infrastructure, you must be granted security access in a policy  by an administrator. This access is required whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you get a message that you don’t have permission or are unauthorized, verify with your administrator what type of access you have and which compartment  to work in.

To get started with Cloud Advisor, an administrator must grant each user access to Cloud Advisor and to the resources that Cloud Advisor recommendations impact through an IAM policy. Each service in Oracle Cloud Infrastructure integrates with IAM for authentication and authorization, for all interfaces (the Console, SDK or CLI, and REST API).

The resource name for Cloud Advisor is optimizer-api-family. The following is an example policy to grant users access to Cloud Advisor to the resources that Cloud Advisor recommendations impact:

Allow group OptimizerAdmins to manage optimizer-api-family in tenancy

If you're new to policies, see Getting Started with Policies and Common Policies. For more information about Cloud Advisor policies, see Policy Details for Cloud Advisor.

Profile Descriptions

Some recommendations allow you to customize the recommendation profile to tailor the recommendations to your requirements. This section describes each profile.

Downsize underutilized compute instances Profiles

The following profiles are available for the Downsize underutilized compute instances recommendation type.

Average Methodology Profile Descriptions

If you choose the average methodology, the mean CPU utilization is used when evaluating compute instances. The profile options with the average methodology are:

  • Conservative (Average): The conservative profile identifies all compute instances that have had the following:

    • an average CPU utilization less than 5%
    • a maximum memory utilization less than 10%
    • a maximum network utilization less than 3%

    Supported VNICs are also considered. If a resize is recommended, the recommended core count has a projected average CPU utilization less than 10%.

  • Standard (Average): The standard profile identifies all compute instances that have had the following:

    • an average CPU utilization less than 10%
    • a maximum memory utilization less than 10%
    • a maximum network utilization less than 3%

    Supported VNICs are also considered. If a resize is recommended, the recommended core count has a projected average CPU utilization less than 20%.

  • Aggressive (Average): The Aggressive profile identifies all compute instances that have had the following:

    • an average CPU utilization less than 15%
    • a maximum memory utilization less than 10%.
    • a maximum network utilization less than 3%

    Supported VNICs are also considered. If a resize is recommended, the recommended core count has a projected average CPU utilization less than 30%.

P95 Methodology Profile Descriptions

If you choose the P95 methodology, a p-value of 95 is used to evaluate the CPU utilization threshold. The profile options with the P95 methodology are:

  • Conservative (P95): The conservative profile identifies all compute instances that have had the following:

    • a P95 CPU utilization less than 5%
    • a maximum memory utilization less than 10%
    • a maximum network utilization less than 3%

    Supported VNICs are also considered. If a resize is recommended, the recommended core count has a projected P95 CPU utilization less than 10%.

  • Standard (P95): The standard profile identifies all compute instances that have had the following:

    • a P95 CPU utilization less than 10%
    • a maximum memory utilization less than 10%
    • a maximum network utilization less than 3%

    Network throughput and supported VNICs are also considered. If a resize is recommended, the recommended core count has a projected P95 CPU utilization less than 20%.

  • Aggressive (P95): The aggressive profile identifies all compute instances that have had the following:

    • a P95 CPU utilization of less than 15%
    • a maximum memory utilization of less than 10%
    • a maximum network utilization less than 3%

    Network throughput and supported VNICs are also considered. If a resize is recommended, the recommended core count has a projected P95 CPU utilization less than 30%.

Downsize underutilized load balancers Profiles

The following profiles are available for the Downsize underutilized load balancers recommendation type. All profile options use the average methodology.

Profile Descriptions

For these profiles, the PeakBandwidth metric is used. Peak bandwidth measures the maximum bandwidth per second used during the specified interval. For more details, see Load Balancer Metrics. Cloud Advisor pulls the metric every three hours and averages the values over the specified evaluation period.

  • Conservative: The conservative profile identifies all load balancers for which the average of the maximum values for peak bandwidth usage over the evaluation period is less than 85% of the minimum network bandwidth.

  • Standard: The standard profile identifies all load balancers for which the average of the maximum values for peak bandwidth usage over the evaluation period is less than 90% of the minimum network bandwidth.

  • Aggressive: The aggressive profile identifies all load balancers for which the average of the maximum values for peak bandwidth usage over the evaluation period is less than 95% of the minimum network bandwidth.

Rightsize compute instances Profiles

The following profiles are available for the Rightsize compute instances recommendation type.

Average Methodology Profile Descriptions

If you choose the average methodology, the mean CPU utilization is used when evaluating compute instances. The profile options with the average methodology are:

  • Conservative (Average): The conservative profile identifies all compute instances that have had both:

    • an average CPU utilization greater than 95% and
    • a maximum memory utilization greater than 95%
  • Standard (Average): The standard profile identifies all compute instances that have had both:

    • an average CPU utilization greater than 80% and
    • a maximum memory utilization greater than 80%
  • Aggressive (Average): The Aggressive profile identifies all compute instances that have had both:

    • an average CPU utilization greater than 60% and
    • a maximum memory utilization greater than 60%
P95 Methodology Profile Descriptions

If you choose the P95 methodology, a p-value of 95 is used to evaluate the CPU utilization threshold. The profile options with the P95 methodology are:

  • Conservative (P95): The conservative profile identifies all compute instances that have had both:

    • a P95 CPU utilization greater than 95% and
    • a maximum memory utilization greater than 95%
  • Standard (P95): The standard profile identifies all compute instances that have had both:

    • a P95 CPU utilization greater than 80% and
    • a maximum memory utilization greater than 80%
  • Aggressive (P95): The aggressive profile identifies all compute instances that have had both:

    • a P95 CPU utilization greater than 60% and
    • a maximum memory utilization greater than 60%

Rightsize load balancers Profiles

The following profiles are available for the Rightsize load balancers recommendation type. All profile options use the average methodology.

Profile Descriptions

For these profiles, the PeakBandwidth metric is used. Peak bandwidth measures the maximum bandwidth per second used during the specified interval. For more details, see Load Balancer Metrics. Cloud Advisor pulls the metric every three hours and averages the values over the specified evaluation period.

  • Conservative: The conservative profile identifies all load balancers for which the average of the maximum values for peak bandwidth usage over the evaluation period is more than 95% of the maximum network bandwidth.

  • Standard: The standard profile identifies all load balancers for which the average of the maximum values for peak bandwidth usage over the evaluation period is more than 85% of the maximum network bandwidth.

  • Aggressive: The aggressive profile identifies all load balancers for which the average of the maximum values for peak bandwidth usage over the evaluation period is more than 75% of the maximum network bandwidth.

Customizing Overrides

Learn how to create and edit overrides of Cloud Advisor recommendations.

Using the Console

To view customizations and overrides
Open the navigation menu and click Governance & Administration. Under Cloud Advisor, click Settings.
To create an override

You can customize recommendations for resources in specific compartments and for resources with certain tags by creating recommendation overrides. You can create up to 50 recommendation customizations, including overrides. To create an override, you must specify at least one compartment or tag.

In addition to the standard Cloud Advisor permissions, to use overrides on compartments, you must belong to a group that has the COMPARTMENT_INSPECT permission. To use overrides with tags, you must belong to a group that has the TAG_NAMESPACE_INSPECT permission. For more information, see Details for IAM without Identity Domains.

  1. Open the navigation menu and click Governance & Administration. Under Cloud Advisor, click Settings.
  2. In the Customizations and overrides section, under Overrides, click Create override.
  3. In the Create new override panel, enter the following information.
    1. For Name, enter a name for the override. The name must be unique.
    2. For Recommendation, in the drop-down menu, select the recommendation that the override applies to. The menu only lists recommendations that are customizable.
    3. In the Recommendation profile section, specify the recommendation profile to use for the resources impacted by this override.
      Important

      The Evaluation period and Methodology fields are only available for some profile types and might not apply.
      • For Evaluation period, select time span that you want Cloud Advisor to use to collect data for recommendations.
      • For Methodology, select either P95 or Average.
      • For Profile, select a profile. See descriptions of the profile options.
    4. In the Compartment overrides section, select up to 10 compartments for this override. The override applies to the resources in the selected compartments.
      1. For Specify compartments, select the method to use to identify the compartment: By name, By OCID, or By path.
      2. In the drop-down menu, select the compartments that the override applies to.
    5. In the Tag overrides section, click Add a tag override. The Add a tag override panel opens. Only defined tags are supported. The tag must be on the compartment, inherited from one compartment to another, or inherited from a compartment to the resource.
    6. In the Add a tag override panel, make the following selections, and then click Add. The override applies to the resources that contain the specified tags.
      1. For Tag namespace, in the drop-down menu, select the tag namespace that contains your tags. Cloud Advisor supports the following characters for the tag namespace field: 0-9, a-z, A-Z, _, @, -, :.
      2. For Tag key, in the drop-down menu, select the name used to refer to the tag. Cloud Advisor supports the following characters for the tag key field: 0-9, a-z, A-Z, _, @, -, :.
      3. For Value, select either Match any value or Match any of the following.
        • If you choose Match any value, the override applies to any resource with the tag selected in the Tag key field.
        • If you choose Match any of the following, in the drop-down menu, select or enter tag values. The override applies only to resources with the tag key and tag values specified. The tag values can contain any UTF-8 characters except single quotation marks.
    7. To add another tag override, click + another tag override and repeat the previous step. You can create up to 10 tag overrides.
  4. Click Create.
To edit a recommendation override
  1. Open the navigation menu and click Governance & Administration. Under Cloud Advisor, click Settings.
    The Cloud Advisor Settings page opens.
  2. In the Customizations and overrides section, in the Overrides table, find the recommendation that you want to edit, click the Actions icon (Actions icon), and then click Edit.
  3. In the Edit override panel, change the override, and then click Save changes.
To edit a global recommendation override

For some recommendation types, you can customize the logic that Cloud Advisor uses. The default configuration uses the standard profile and the average methodology.

Note

Changes made to your recommendation settings will take effect the next time Cloud Advisor runs for your tenancy.
  1. Open the navigation menu and click Governance & Administration. Under Cloud Advisor, click Settings.
    The Cloud Advisor Settings page opens.
  2. In the Customizations and overrides section, in the Global recommendations table, find the row for the recommendation that you want to customize, click the Actions icon (Actions icon), and then click Customize.
    A Customize recommendation logic panel opens.
  3. In the Customize recommendation logic panel, make the following selections (if applicable), and then click Save changes.
    Important

    The Evaluation period and Methodology fields are only available for some profile types and might not apply.
    • For Evaluation period, choose the time span that Cloud Advisor should use to collect data for recommendations.
    • For Methodology, select either P95 or Average.
    • For Profile, select a profile. See descriptions of the profile options.
    Changes made to your recommendation settings take effect the next time Cloud Advisor runs for your tenancy.
To delete an override
  1. Open the navigation menu and click Governance & Administration. Under Cloud Advisor, click Settings.
    The Cloud Advisor Settings page opens.
  2. In the Customizations and overrides section, in the Overrides table, find the recommendation that you want to delete, click the Actions icon (Actions icon), and then click Delete.
  3. In the confirmation dialog, click Delete.

Profiles

Learn how to view and create profiles.

Getting Profiles

Using the CLI

Use the oci optimizer profile get command to get a specified profile.

oci optimizer profile get --profile-id <profile_ocid>

For a complete list of flags and variable options for CLI commands, see the Command Line Reference.

Using the API

Use the GetProfile operation to get a specified profile.

Creating Profiles

Using the CLI

Use the oci optimizer profile create command to create profiles.

oci optimizer profile create --compartment-id <compartment_ocid> --description <text> --levels-configuration <file://path/to/file>  --name <text>

For a complete list of flags and variable options for CLI commands, see the Command Line Reference.

Using the API

Use the CreateProfile operation to create profiles.

Editing Profiles

Using the API

Use the UpdateProfile operation to update profiles.

Deleting Profiles

Using the API

Use the DeleteProfile operation to delete profiles.