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.
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.
Tags: A dropdown of all tags available from AWS.
Includes Any or All filters and Inclusion/Exclusion filters.
Attributes: A dropdown of all attributes available from AWS.
Includes Any or All filters and Inclusion/Exclusion filters.
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:
Deselect ServiceNow as the change management service for the policy
Enable or disable default parameter settings
Options are: enabled or disabled
Add, delete, or modify optional parameters
Jira settings
You can modify the following settings for ServiceNow:
Deselect Jira as the change management service for the policy
Enable or disable default parameter settings
Options are: enabled or disabled
Add, delete, or modify optional parameters
Related Topics
Constraints define the minimum requirements based on numerical settings or historical utilization.
You set constraints separately for Virtual Machines and for Containers.
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.
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.
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
No Constraint: Returns all possible recommendations for resources with the attribute Graviton CPU.
Dynamic: Returns recommendations either including or excluding resources with the attribute Graviton CPUs.
Only Graviton CPU
Exclude Graviton CPU
No Change
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.
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