RightSizing (Recommend specifications)
Right Sizing Recommended Specifications
This function recommends appropriate specifications (downsizing or upsizing) based on resource monitoring data.
On 2025-09-22, AWS ElastiCache optimal specification recommendations and Azure OpenAI optimization features were added.
Cache
As the cost of using AWS ElastiCache increases, the importance of cost optimization has increased, and appropriate specification features have been added.
Recommended in the same way as server/database
AI
As Azure OpenAI usage grows, the need for optimization grows, so optimization features have been added.
Please refer to the document below for detailed guide.
As of 2024-09-26, the detection criteria for recommended appropriate specifications have been improved.
CloudXper has been improved to provide as many recommendations as possible based on the data it has.
Improvements
Changed from a recommended designated data source to a preferred data source recommendation method.(Server only)
Existing: If the data source for the detection criteria was not recommended (insufficient data, no data (CMS not installed)), appropriate specifications were not recommended.
EX) Select data source “CMS”, if CMS agent is not installed on the server → “CMS not installed” is displayed.
Change: If the priority data source for the detection criteria is not recommended (insufficient data, no data (CMS not installed)), recommendations will be made through other data sources.
EX) First, select the data source “CMS”. If the CMS agent is not installed on the server but CSP data can be recommended, it is recommended.
We have relaxed the data insufficiency criteria and enabled you to directly set the data insufficiency criteria (operating rate within the analysis period).
Existing: Only the analysis period can be set, and the operating rate cannot be set, so it is recommended only when there is data of “80%” or more according to the default condition or “20%” or more depending on the setting.
EX) Even if CPU data is “90%” and MEM data is “50%” within 93 days, recommendation is not possible due to “insufficient data”.
Change: You can now directly set the operating rate within the analysis period, and the basic condition has been changed to recommend when it exists at 20% or more within 93 days.
EX) Even if CPU data is “30%” and Memory data is not present (Memory Agent not installed), appropriate specifications can be recommended based on CPU data.
Detection criteria conditions have been removed. Conditions such as "CPU" and "MEM" have been removed, and the default condition has been fixed to "OR."
Existing: In case of “AND” condition, it was recommended that both CPU and Memory should have the same condition.
EX) CPU: “Upsizing” condition, Memory: Normal → Displayed as Normal
Change: “CPU”, “MEM” conditions are gone and default “OR” condition works.
EX) CPU: “Upsizing” condition, Memory: Normal → Displayed as “Upsizing”
caution : Since the “Upsizing” condition has a higher priority than the downsizing condition, if there is an “Upsizing” recommendation indicator, it will be displayed as “Upsizing”.
EX) CPU: “Upsizing” condition, Memory: “Downsizing” condition → Displayed as “Upsizing”
1. RightSizing screen
1.1 RightSizing detection target resource
Provides RightSizing capabilities for servers and databases.
Server: AWS EC2, Azure Virtual Machine, GCP VM Instance
Database: AWS RDS, GCP Cloud SQL
Cache: AWS Elasticache
AI: Azure OpenAI
1.2 Setting detection criteria
1.2.1 Setting server detection criteria
CMS: Cloud Monitoring System. This is the default data source and requires the installation of a CMS agent to use it.
CSP: Data metrics provided by AWS, Azure, and GCP. After changing the detection conditions to CSP, select the CPU condition to use it without installation.
(※ However, to check memory indicators, you must install a cloud self-monitoring agent such as AWS CloudWatch.)
1.2.2 Setting Database/Cache Detection Criteria
1.3 RightSizing Detection Summary
Provides a summary of the results of the appropriate specification recommendation for all resources.
Downsizing: The server is designated as a downsizing target server if the detection criteria are met (downsizing).
Upsizing: The server is designated as the target server for upsizing when the detection criteria are met (upsizing).
Normal: The number of normal servers that do not meet the detection criteria.
Insufficient data: Number of servers with insufficient uptime within the detection criteria period.
No data: The number of servers for which usage from the data source has not been collected for more than 3 days.
Excluded: Included in the recommendation target, but excluded by the user through settings (Ignore)
Total: Number of servers including all of the above items
Detection Criteria: You can set the analysis period, whether to include upsizing, downsizing, and instance type changes, etc. (The detection criteria will be applied in real time after changing them.)
1.4 Resource Distribution Status
You can check the resource distribution status of recommended servers through RightSizing (default: only recommended targets are included)
Target: Recommended, Normal, All selectable (Default: Recommended)
Indicator: Average or maximum hourly value (default: average of maximum hourly value)
1.5 Status by account
You can check the RightSizing information per cloud account.
1.6 History
You can check the history of changes to recommended rules or resource specifications, and you can even check detailed information when selecting (compare before/after changes).
1.7 RightSizing Detection Results and Details
RightSizing provides a list of target resources for detection and the basis for recommendations (monitoring performance data), and allows filtering and searching based on search purpose/conditions.
You can check the detailed performance pattern basis by clicking the arrow View Details button in the Metrics column in the query results.