The Cost Saving Opportunities page provides reports with recommendations to reduce costs in your cloud environment. There are two basic recommendations: one for idle resources and one for right sizing.
Default reports are generated when a new account (instance) is added in Cloud Cost Management (CCM) and emailed to the user who set up the instance. Afterward, the reports are automatically generated weekly. These reports are emailed to anyone who is a member of the organization that is associated with the instance.
Note
Sometimes the settings for a report do not apply to any resources in your environment. When that happens, the report will be empty, displaying no results. If the report is set up for email, a report might not be sent.
The Idle Resources report identifies cloud resources that are either no longer attached to an instance, or are attached to a stopped instance. Although the resources are not being used, you are still being charged for them, so having a view into those idle resources can save on your cloud spend. The Idle Resources report provides information to assist in determining if the resource should be removed, reassigned, etc. Idle resources are recalculated daily.
The Right Sizing report includes a high-level dashboard overview of potential cost savings. It also provides a table that lists details about recommended savings. This report can help you identify underutilized instances and determine which alternative instance types might reduce unnecessary expense. Right-sizing recommendations are recalculated weekly.
Some parameters for the Idle Resources and Right Sizing reports can be modified by assigning policies to a data source.
Note
Virtana Platform reports display currency only in US dollars (USD}. To accurately reflect costs, ensure your data sources have the currency display set to US dollars in the AWS or Azure portal. For Azure, see Set the Currency Option in Azure to USD.
Related Topics
Cost Saving Opportunities Page
When determining if changes should be made to your environment, a good place to start is the Cost Saving Dashboard. This quick-view dashboard provides a simple overview of potential savings.
Tip
With a new AWS integration, it can take up to 24 hours for initial AWS CUR data to be available to Virtana Platform. If data is not displayed or updated after 24 hours, verify that your new AWS integration is properly configured.
The cost savings displayed in the dashboard is a comparison of costs for the current month versus the previous month.
For AWS, idle resource recommendations are generated for unattached Elastic Block Store (EBS), EBS on Stopped EC2 compute instances, unattached Elastic Load Balancing (ELB), and unattached Elastic IP addresses.
For Azure, idle resource recommendations are generated for unattached applications, disks on stopped VMs, unattached load balancers, and unattached static public IPs.
For right sizing, recommendations are provided for AWS EC2 instances and Azure VMs.
Cost Saving summary widgets include the following:
-
Current Cost gives you a comparison of the current month's and previous month's overall cost in US dollars. Also indicates the percentage that costs have increased or decreased. A red "up" arrow indicates increased costs and a green "down" arrow indicates decreased costs.
-
Idle Resources displays in US Dollars how much you can save per month by eliminating unused cloud resources, along with the percentage of increase or decrease compared to last month.
-
Right Sizing indicates the monthly cost savings in US dollars that would result from modifying your resources per the recommendations, along with the percentage of increase or decrease compared to last month.
-
Total Savings Available reflects the combined monthly savings in US dollars that could be achieved by eliminating idle resources and implementing right sizing recommendations.
Cost Saving Opportunities (CSO) provides an easily scannable overview of potential savings on your cloud spend.
From this page you can view recommendations for savings regarding idle resources and right-sized resources.
Some things you can do with CSO reports:
-
View a summary of potential cost savings on a dashboard
-
Identify Idle Resources that might be removed or reassigned
-
Determine which resources are being under- or over-utilized and might be resized to potentially improve performance or reduce costs
-
Track short and long-term spending trends with the period comparison view
-
Compare the cost of a certain service in relation to your whole services portfolio with the stacked view
-
Identify which policy is assigned to a compute instance
-
Determine if change requests have been or need to be submitted
From the Cost Saving Opportunities page you perform the following actions:
-
Create, edit, and save CSO report settings
-
View report data in graphical or tabular form
-
Edit and save report filters
-
Edit and save Idle Resources and Right Sizing policies
-
Enable/disable or modify the change management settings in policies
-
Schedule CSO reports for emailing
The Cost Saving dashboard offers a high-level view of your environment.
If your cloud environment is optimized and no right-sizing recommendations are available, then the Right Sizing card displays the word Optimized, with a green checkmark.
Tip
Right-sizing savings might differ from week to week because of different workloads on the selected entities.
Some things you can do using policies for idle resources and right sizing include the following:
-
Select the data sources to which the policy should apply.
-
Select a change management system for change requests, enable or disable the change request feature, and modify default settings for change requests.
-
Add or modify the optional constraints to guide the recommendation results and discover other use-case driven savings opportunities.
-
Preview the potential results of policy changes.
The default Idle Resources report displays a list of all unattached resources, as well as resources attached to stopped cloud instances. The resources are sorted by monthly cost (highest to lowest). The report displays an image of the resources at the point in time the report was run.
The report can be sorted by any field. Click on the column header to sort by the field in ascending or descending order.
To view further details about any entity in the table, open the accordion for that entity.
The Policy column in the Recommendation Details table contains a clickable badge 
that opens the configuration for the active policy. If no custom policies are created, the link opens the default policy. You can view or modify the policy settings.
The Change Request column indicates if a change request can be or has been submitted. If not yet submitted, a Change button displays. If the request has been submitted, the change request ID displays.
Using policies, you can add optional constraints to define idle resources and set thresholds. This allows you to fine-tune idle resource reporting. For example, you can identify only idle resources of higher cost, or avoid capturing resources that are idle by design
Each recommendation found in your Right Sizing report compares the attributes and utilization of an instance against the most currently available AWS or Azure SKU library. Cloud Cost Management (CCM) then determines what combination of CSP features would best suit your existing workload needs. You can set constraints for right sizing to ensure recommendations do not impact performance.
In the Recommendations table, rows highlighted in gray indicate one of the following.
-
No recommendations have been set.
Cost and Savings columns in the Details table will display "--".
-
Recommendations have been calculated for those entities, but there are no savings recommendations (those entities are already optimized).
Projected Savings columns in the Details table will display a value of "0".
-
Recommendations have been calculated for those entities, but the policy constraints do not allow the recommendations to be implemented.
Cost and Savings columns in the Details table will display a monetary value in USD.
If recommendations are inactive (grayed out), it is because some constraints assigned in the policy are not met for the indicated entities.
For example, assume the right sizing policy constraint for Recommendation Aggressiveness is set to Propose only savings greater than 50%. In this case, the entities with savings less than 50% would be highlighted in gray and have no active recommendations.
On the Right Sizing tab you can easily compare week-to-week savings. If you click the date range above the Right Sizing table, you can see the Right Sizing Analysis Range. If you select a date range, Cloud Cost Management (CCM) recalculates the savings results for the selected period against the latest policy applied to the compute instance. If changes were made to the policy after the time when the report data was initially captured, those changes will be reflected in the recalculated output and might change the projected savings value.
Note
When viewing recommendations for Kubernetes, the Current Type and Proposed Type columns display recommended values, based on the Kubernetes configurations for CPU and memory. CPU and memory values are set in the configuration file, as shown in the Kubernetes documentation.
The following image show examples of Kubernetes recommended values, displayed as CPU-memory, such as 1000mCPU-128MiB. CPU values are in milli-CPUs.
Kubernetes metrics that are scraped by Prometheus are updated in CCM once a week.
Some additional constraints, that cannot be modified, are implemented by default on all right-sizing calculations. For example, right-sizing recommendations assume that the region configured by the user should not change, so recommendations will be kept within the existing assigned regions. Neither does right-sizing address preinstalled licensing, such as a pay-as-you-go Windows license, so license considerations are not included in recommendations.
You can see more detail about a specific compute instance by expanding the accordion in the table.
The Policy column in the Recommendation Details table contains a clickable badge that opens the configuration for the active policy. If no custom policies are created, the link opens the default policy. You can view or modify the policy settings.
The Change Request column indicates if a change request can be or has been submitted. If not yet submitted, a Change button displays. If the request has been submitted, the change request ID displays.
Related Topics
Cloud Cost Management (CCM) includes Default reports for Cost Saving Opportunities (CSO). You can view or email reports that contain CSO recommendations. However, you cannot directly modify a CSO report. You can view reports with a read-only role.
Although the Default report settings cannot be modified, you can apply policy settings to the reports to set constraints for the report output. Creating policies requires an administrator role.
About This Task
To complete this task, you must select a report filter and then edit and save the report settings.
Prerequisites
You should be familiar with the use of tags and attributes in CCM before creating or editing reports. See Filtering in Virtana Platform and Filtering and Grouping Options for more information.
Note
Virtana Platform reports display currency only in US dollars (USD}. To accurately reflect costs, ensure your data sources have the currency display set to US dollars in the AWS or Azure portal. For Azure, see Set the Currency Option in Azure to USD.
Steps
-
In the CCM module, navigate to Cost Saving Opportunities.
-
Select a report Filter that is associated with the data source you want.
-
To change the data source for the report, click the report Filter Edit button.
-
Add or remove resources under Data Sources or use the Filter Entities option to reduce the scope of the report.
-
Apply the configuration and Save, if desired.
-
On the Right Sizing tab, click the time range selector to view data for different time periods.
You cannot modify the time range for Idle Resources reports. Only the most recently identified idle resources display.
-
Other actions you can perform from this page:
-
View and edit any policies associated with compute instances in the Recommendation Details table.
Administrator role is required to edit policies.
-
Download the report as a CSV file.
-
Email a copy of the report for the current week.
You can view, but cannot email, reports for prior weeks.
Tip
If you want a copy of a right sizing report from a prior week, you can take a screenshot.
-
You can view or manually implement a change request, if the feature is enabled.
-
Related Toipics
Idle Resources reports are accessed from the Cost Saving Opportunities page. Use these reports to keep track of your unused cloud resources. You can access reports for AWS and Azure cloud providers and for their various resource types (on-demand, reserved, etc.).
The report shows you a snapshot of the idle resources at the point in time the report was run. Reports are run daily at 11:00 UTC.
You can customize reports based on entity type, and you can set thresholds to define what is considered "idle" for resources in your environment. Once your reports are created and saved, you can email them to appropriate recipients.
In addition to any native tools that might collect idle time data on your CSP, Cloud Cost Management (CCM) also collects and stores idle resource information in a database. The CCM database provides idle time information if native tools, such as CloudTrail, are not enabled or not available.
Azure Reports
For Azure instances, Idle Resources reporting is available for disks, public IPs, application gateways, and load balancers. The report displays the following:
-
For disks: Resources that are unattached or attached to stopped VMs.
Possible Idle Types: Unattached, On Stopped VM
-
For Public IP addresses: Network interfaces that have a static public IP associated but the IP is unattached, and network interfaces that don't have a public IP.
Possible Idle Types: Static
-
Application gateway: Resources that are in a stopped state, are running but don't have backend services or frontend IP, are running but don't have listeners.
Possible Idle Types: Stopped, Missing Backend Config, Missing Frontend Config, Missing Listeners
-
Load balancer: Resources without rules set, don't have frontend IP, no backend service, and no health probes set. Note: There is no way to determine the running state of the load balancer.
Possible Idle Types: Missing Load Balancing Rules, Missing Backend Config, Missing Frontend Config, Missing Health Probe Config
Azure idle resource data is provided by the CCM database only.
AWS Reports
For AWS instances, Idle Resources reporting is available for EBS resources, Elastic IP resources, and ELB resources. The report displays the following:
-
For EBS: Resources that are not attached to an EC2 instance and those that are attached to stopped EC2 instances.
-
Elastic IP: Resources that are not associated with any EC2 instance or are attached to stopped EC2 instances.
-
For ELB: Resources that do not have EC2 instances attached to them.
Possible Idle Types: None (cell is blank in the idle resources table)
The ELB report includes the following resources:
-
Application Load Balancer (ALB)
-
Network Load Balancer (NLB)
-
Classic Load Balancer (CLB)
-
Information about AWS resource idle time can be collected in AWS CloudTrail, as well as the CCM database. Idle time for AWS resources is determined first by checking CloudTrail data, if CloudTrail is enabled on AWS.
If CloudTrail data is unavailable or is incomplete for any of the resources, then CCM can check its database for information. CCM can then report on resources for which idle times are definitively known, as well as on resources with an estimated idle period. The policy option "Include when idle period is unknown" allows you to enable or disable the inclusion of the CCM-estimated idle resources in AWS report results.
Related Topics
Cost Saving Opportunities Page
Idle Resources Policy Parameters
In addition to any native tools that might collect idle time data on your CSP, Cloud Cost Management (CCM) also collects and stores idle resource information in a database. The CCM database provides idle time information if native tools, such as CloudTrail, are not enabled or not available.
CCM can also provide approximations for idle times when complete data is not available for any resources. An example of this would be if a policy is set to report idle resources only after being idle for 10 days, but your Virtana Platform integration has only been active for 7 days.
For Azure, we calculate idle period from our database. When a resource has been idle from the beginning of our observations, we assume that the full idle period is unknown. Otherwise, we calculate the exact idle period.
For AWS, we use CloudTrail to get the exact idle period. CloudTrail stores the data for the past 90 days. So, when the resource is idle for more than 90 days, the full idle period is unknown. The exact idle period can be determined when the resource is idle for less than 90 days
If CloudTrail is turned off for your account, we calculate idle period from our database. when a resource has been idle from the beginning of our observations, we assume that the full idle period is unknown. Otherwise, we calculate the exact idle period.
These policy settings, or "rules", impact the output of your Idle Resources reports. You can modify the Default policy parameters to customize report output. As you define the report criteria, the impact of potential changes are shown on the Affected Entities Preview tab.
You must have administrator privileges to modify a policy.
General Parameters Tab
General Policy Parameters
Scope of Analysis
The policy parameter that allows you to select which instances or entities (scope) the policy applies to. Settings include the CSP data source and applicable filters.
-
Data Source: An expandable list from which you select cloud provider instances, such as AWS EC2 or Azure VMs. Selecting an instance automatically selects all linked child instances.
-
Entity Filter: Select to Include Entities or Exclude Entities by tag or attribute.
Change Requests
If you configured a change management integration with Virtana Platform, then you can submit ticket requests to modify your CSP environment based on recommendations from Idle Resources or Right Sizing Reports. These parameters identify the fields to include when submitting a specific type of request.
You can modify the settings for ServiceNow or Jira change management integrations from this section of the form.
ServiceNow settings
The exact fields and values that display in this section depend upon the configuration of the default settings in the change management integration in Settings.
You can modify the following settings for ServiceNow:
Jira settings
The exact fields and values that display in this section depend upon the configuration of the default settings in the change management integration in Settings.
You can modify the following settings for Jira:
Constraints Tab
Resources
-
Entity Type
Identifies the following entity types:
For AWS
-
Unattached EBS
-
Unattached ELB
-
EBS on Stopped EC2
-
Unattached Elastic IP (EIP)
For Azure
-
Unattached Application
-
Azure Disk on Stopped VM
-
Unattached Load Balancer
-
Unattached Public IP
-
-
Report as idle after
-
Enter a numerical value for the days.
-
Enable or disable "Include when idle period is unknown".
This option is useful for circumstances when an idle period is not definitively known. This could include when a native tool such as AWS CloudTrail is disabled, or when information about the resource has not been collected for as long as the "Report as idle after" period setting in CCM.
When this option is enabled, CCM reports on all resources known to be idle for greater than or equal to the idle period setting, as well as resources for which idle time is less than the idle period setting. For example, if you have 5 Unattached Azure Disks and the idle period is set to 10 days, but data has been collected by Virtana Platform for 7 days, the report will display results for all 5 disks. The results will indicate when data is based on estimated time rather than exact time.
If the option is disabled, the report will include only resources that have idle times greater than or equal to the idle period setting. So, using the above example, only 4 disks would be included in the results.
-
-
If monthly cost is greater than
-
Enter a numerical value in US dollars to limit the results to only entity types with a monthly cost greater than the amount entered.
-
Affected Entities Preview Tab
This tab on the policy configuration form provides a preview of the impact your changes would have if implemented. Each affected entity is identified and listed, along with current property settings, recommended changes. and potential savings.
Following is an example of the type of information provided on this tab.
Properties listed in Affected Entities Preview:
-
Entity
Example: VM
-
Name
Name assigned to the entity.
-
Cloud
Example: AWS or Azure
-
Projected savings
Provided as a US dollar amount.
-
Recommendation
Possible values: No Change (less than 5% savings), Active, Remove Idle Resource
-
Properties listed in the accordion row for each entity type
Click the accordion arrow to access the entity details.
AWS Volumes
-
Size in GB
-
Volume ID
-
Account ID
-
IOPS
-
Type (ex.: gp2, Microsoft compute/disks, etc.)
-
Idle Period
Azure Application Gateway
-
If a row is colored gray in the table, it indicates that there are no recommended changes resulting from the modifications made to the policy.
Related Topics
Right Sizing is the practice of finding the perfect balance between cost efficiency and stability for each of your resources. The Virtana Platform Cloud Cost Management (CCM) module provides several tools that help you understand the current performance of your workloads and their true needs—both now and in the future.
With Right Sizing reports, you can view details about your CSP instances to determine what actions you might want to take to improve efficiency, save money, etc. Right Sizing checks daily for updates, but runs a report once a week on Sundays at 13:00 UTC.
The 7-day timeframe for Right Sizing reports is optimal. If the report cycle were fewer than 7 days, you could miss key events, such as a back-up that occurs once a week. A longer time period could result in undersizing a resource, as the number of days the resource is less active could increase and dilute the overall utilization analysis.
On the Right Sizing tab you can easily compare week-to-week savings. If you click the date range above the Right Sizing table, you can see the Right Sizing Analysis Range. If you select a date range, Cloud Cost Management (CCM) recalculates the savings results for the selected period against the latest policy applied to the compute instance. If changes were made to the policy after the time when the report data was initially captured, those changes will be reflected in the recalculated output and might change the projected savings value.
Viewing AWS Data in Reports
Use the Right Sizing report to analyze cost data across all of your consolidated or linked AWS accounts. Right Sizing assesses your current usage and recommends changes to potentially improve performance or reduce costs. The report provides a comparison of current costs and proposed costs based on the current instance type being used and a proposed instance type.
Each recommendation found in your AWS EC2 Right Sizing report compares your EC2’s attributes and utilization against the most currently available AWS SKU Library to determine what combination woud best suit your existing workload needs. You can also add optional constraints (such as CPU utilization not exceeding a particular level) to guide our recommendation results and discover other use-case driven savings opportunities.
Viewing Microsoft Azure Data in Reports
Compare your current virtual machines against Azure’s most recent SKUs to find the best fit for your workloads and your budget. The Azure VM Right Sizing report enables you to leverage your historic workloads to truly right-size your resources.
You can add optional constraints (such as CPU utilization limits) to further contextualize recommendations and highlight different savings opportunities across your portfolio.
Related Topics
Cost Saving Opportunities Reports
Right Sizing Policy Parameters
These policy settings impact the output of your Right Sizing Recommendations reports. As you define the report criteria, you can preview report updates on the Affected Entities Preview based on the constraints you select.
You can modify the Default policy parameters to visualize "what if" scenarios. For example, you can compare the results of increasing or decreasing the recommendation aggressiveness, or restricting memory so it cannot decrease versus making recommendations based on historical utilization, etc.
If parameter values are set that cannot be met by some entities, those entities display in the Recommendations table with gray highlighting. This indicates that no active recommendations are possible for the highlighted entities.
An example of a constraint that would result in no active recommendations is if you set minimum memory to 50 GB, but the required instance type is set to T3a.small, which does not have 50GB of memory.
Some additional constraints, that cannot be modified, are implemented by default on all right-sizing calculations. For example, right-sizing recommendations assume that the region configured by the user should not change, so recommendations will be kept within the existing assigned regions. Neither does right-sizing address preinstalled licensing, such as a pay-as-you-go Windows license, so license considerations are not included in recommendations.
General Parameters Tab
General Policy Parameters
Scope of Analysis
The policy parameter that allows you to select which instances or entities (scope) the policy applies to. Settings include the CSP data source and applicable filters.
-
Data Source: An expandable list from which you select cloud provider instances, such as AWS EC2 or Azure VMs. Selecting an instance automatically selects all linked child instances.
-
Entity Filter: Select to Include Entities or Exclude Entities by tag or attribute.
Change Requests
Change Requests
If you configured a change management integration with Virtana Platform, then you can submit ticket requests to modify your CSP environment based on recommendations from Idle Resources or Right Sizing Reports. These parameters identify the fields to include when submitting a specific type of request.
You can modify the settings for ServiceNow or Jira change management integrations from this section of the form.
ServiceNow settings
You can modify the following settings for ServiceNow:
Jira settings
You can modify the following settings for ServiceNow:
Related Topics
Right Sizing Constraints Tab
Constraints define the minimum requirements based on numerical settings or historical utilization.
You set constraints separately for Virtual Machines and for Containers.
Virtual Machines
Basic Right Sizing Constraints
Recommendation Aggressiveness
-
Propose only savings greater than a specified percentage in US dollars.
CPU & Memory Data Aggregation
Choose a context for how historical utilization data is applied to recommendations.
-
Maximum: Considers the behavioral maximum demonstrated in utilization data, regardless of rarity.
-
Mean: Considers the behavioral mean demonstrated in all utilization data.
-
95th Percentile: Considers the behavioral norm demonstrated in utilization data (without edge cases).
CPU
The following constraints can be applied to more strictly define your minimal resource requirements for CPUs.
-
No Constraints: Returns all possible recommendations for resources assigned the CPU attribute.
-
CPUs cannot decrease : Returns recommendations where maximum resource utilization is at or below the input amount.
-
Minimum CPUs: Returns recommendations where minimum resource utilization is at or above the input amount.
-
Resize based on historical utilization: Returns recommendations based on historical utilization of the given resource type.
-
Target CPU utilization: Set a specific utilization target as a percentage of CPU resources. Returns recommendations that closely match the target CPU utilization percentage.
-
Memory
The following constraints can be applied to more strictly define your minimal resource requirements.
-
No Constraints: Returns all possible recommendations related to memory.
-
Memory cannot decrease: Returns recommendations where maximum resource utilization is at or below the input amount.
-
Minimum memory (GB): Returns recommendations where minimum resource utilization is at or above the input amount.
-
Resize based on historical utilization: Returns recommendations based on historical utilization of the given resource type.
-
Default memory utilization when diagnostic monitoring not enabled: Specify memory utilization (by percent) when it does not exist because diagnostic monitoring has not been enabled on the cloud provider. Returns recommendations based on an assumption (as a percentage) of memory utilization.
If diagnostic metrics are not enabled and this option is not enabled, then no memory utilization data can be provided.
60% is the recommended setting unless a more accurate percentage is determined.
-
Target memory utilization: Set a specific utilization target as a percentage of memory resources. Returns recommendations that closely match the target memory utilization percentage.
-
Instance Type Constraints
You can specify target instance types (e.g., a series) that can be proposed by the Right Sizing Report. This section displays instance types based on the report's data source type (AWS, Azure, etc.).
-
No Constraint, select from all available instance types: Returns all possible recommendations for the given resource.
-
Do not change series
When. selected, recommendations will retain the same CSP series type.
-
Include selected instance types only.
-
Exclude specific instance types.
Other Resource Constraints
-
Network
-
No Constraint: Returns all possible recommendations for the given resource.
-
Network performance cannot decrease: Returns recommendations where network performance is at or above existing level.
-
Minimum peak network performance (Gbps): Returns recommendations where network performance does not go below the input peak level.
-
-
Disk I/O
-
No Constraint: Returns all possible recommendations for the given resource.
-
Peak IOPS cannot decrease: Returns recommendations where IOPs are at or above existing level.
-
Minimum peak IOPS: Returns recommendations where IOPs does not go below the peak level.
-
-
EC2 Entities: Tenancy
-
No Constraint: Returns all possible recommendations for the given attribute.
-
Shared: Returns only shared tenancy options.
-
Dedicated: Returns only dedicated tenancy options.
-
Host: Returns only host tenancy options.
-
-
EC2 Entities: Term Type
-
No Constraint: Returns all possible term recommendations for the given attribute.
-
Reserved: Returns only recommendations with reservation terms.
-
Reservation Offering Class: Options include Any, Standard, or Convertible.
-
Reservation Contract Length: Options include Any, 1 year, or 3 years.
-
Reservation Purchase Option: Options include Any, No Upfront, All Upfront, Partial Upfront.
-
MS SQL Server: Options include Any, NA, SQL Ent, SQL Std, SQL Web.
-
-
OnDemand: Returns only recommendations with On-Demand terms.
-
-
EC2 Entities: Graviton CPU
Containers
Basic Right Sizing Constraints
CPU & Memory Data Aggregation
Choose a context for how historical utilization data is applied to recommendations.
-
Maximum: Considers the behavioral maximum demonstrated in utilization data, regardless of rarity.
-
Mean: Considers the behavioral mean demonstrated in all utilization data.
-
95th Percentile: Considers the behavioral norm demonstrated in utilization data (without edge cases).
CPU
The following constraints can be applied to more strictly define your minimal resource requirements for CPUs.
-
No Constraints: Returns all possible recommendations for resources assigned the CPU attribute.
-
CPUs cannot decrease : Returns recommendations where maximum resource utilization is at or below the input amount.
-
Minimum CPUs: Returns recommendations where minimum resource utilization is at or above the input amount.
-
Resize based on historical utilization: Returns recommendations based on historical utilization of the given resource type.
-
Target CPU utilization: Set a specific utilization target as a percentage of CPU resources. Returns recommendations that closely match the target CPU utilization percentage.
-
Memory
The following constraints can be applied to more strictly define your minimal resource requirements.
-
No Constraints: Returns all possible recommendations related to memory.
-
Memory cannot decrease: Returns recommendations where maximum resource utilization is at or below the input amount.
-
Minimum memory (GB): Returns recommendations where minimum resource utilization is at or above the input amount.
-
Resize based on historical utilization: Returns recommendations based on historical utilization of the given resource type.
-
Default memory utilization when diagnostic monitoring not enabled: Specify memory utilization (by percent) when it does not exist because diagnostic monitoring has not been enabled on the cloud provider. Returns recommendations based on an assumption (as a percentage) of memory utilization.
If diagnostic metrics are not enabled and this option is not enabled, then no memory utilization data can be provided.
60% is the recommended setting unless a more accurate percentage is determined.
-
Target memory utilization: Set a specific utilization target as a percentage of memory resources. Returns recommendations that closely match the target memory utilization percentage.
-
Affected Entities Preview Tab
This tab on the policy configuration form provides a preview of the impact your changes would have if implemented. Each affected entity is identified and listed, along with current property settings, recommended changes. and potential savings.
Properties listed in Affected Entities Preview:
-
Entity
Example: VM
-
Name
-
Cloud
Example: AWS or Azure
-
Projected savings
Provided as a US dollar amount.
-
Projected savings
Provided as a percentage
-
Recommendation
Possible values: No Change (less than 5% savings), Active
-
Properties listed in the accordion row for each entity type
-
Property type
Examples: Family, CPU Utilization, Active Hours, etc.
-
Current setting or value for each property type listed
-
Proposed or projected setting or value
Indicates whether the change would result in an increase or decrease in a value for each property type listed
-
Related Topics
Comments
0 comments
Article is closed for comments.