Rightsizing resources
Summarize
Summary of Rightsizing Resources
The Rightsizing feature helps optimize resource usage by recommending appropriate sizes for resources that are either over-provisioned or underutilized. Each recommendation comes with a confidence rating and predicted savings, enabling informed decision-making for cost management.
Show less
Key Features
- Scheduling Rightsizing Jobs: Users can schedule jobs to resize specified resources based on analysis from the Rightsizing recommendations page.
- Integration with Change Management: Rightsizing operations integrate directly with ServiceNow's Change Management, allowing for auto-approval or manual approval processes.
- Resource Operations: The system stops, resizes, and restarts resources as needed. If resizing fails, a rollback is performed.
- Recommendations Generation: Rightsizing analysis covers various resources, including Virtual Machines, SQL Databases, and RDS Databases across different cloud providers.
- Confidence Levels: Each recommendation has a confidence level (high, medium, low) based on usage data and resource family/generation similarities.
Key Outcomes
By utilizing the Rightsizing feature, ServiceNow customers can effectively reduce costs associated with over-provisioned resources, utilize resources more efficiently, and make data-driven decisions based on confidence ratings in the recommendations provided. Customers should note limitations, such as the inability to perform Rightsizing on stopped AWS RDS databases, and consider the confidence levels when deciding on resource adjustments.
The Rightsizing feature analyzes resource usage to recommend better sizes for resources that are wasting money by being over-provisioned or underused. A confidence rating and predicted savings support each recommendation. Schedule Rightsizing jobs to resize the resources you specify.
How Rightsizing works
The system updates Rightsizing recommendations each time that billing and usage data are updated.
- On the Rightsizing recommendations page, select the resources to rightsize based on your analysis of the recommendations. For more information, see Resize resources with Rightsizing.
- Add the resources to a Rightsizing job. The job can be a new or an already-defined one.
- Specify the date and time for the job to run.
- Specify the type of approval required for the Rightsizing action.
Rightsizing operations are directly integrated with the ServiceNow Change Management feature.
- Auto-approval: Generates a Standard Change request and the change request is auto-approved.
- Manual approval: Generates a Normal Change request and the appropriate user approves the change request.
- Save the job.
When you save the job, the system immediately generates the change requests. Later, at the scheduled time, the system runs the job. The job performs the following operations:
- For each approved change, resize the resource. For a resource in the ON state, stop the resource, resize it, and then restart it. If the attempt to resize fails, perform a rollback. For more information, see AWS only – Rollback on failed Rightsizing attempts.
- Update the Rightsizing reports with new recommendations and with approved, successful, pending, rejected, and failed changes.
For pending, rejected, and failed change requests, you can reschedule the resources into another job.
How Cloud Cost Management generates Rightsizing recommendations
Recommendations
The Cloud Cost Management application can generate recommendations for Virtual Machines (AWS, Azure, GCP), SQL Databases (Azure, GCP), and RDS Databases (AWS). CPU, memory, and network usage metrics are used to generate database rightsizing recommendations for the database resources.
- Cloud category - AWS Elastic Block Store for Storage Volumes: Service category is storage.
- Cloud category - Azure Disk for Storage Volumes: Service category is storage.
Confidence levels in recommendations
- High confidence requires the following conditions:
- The system has 10 or more days of usage data for the resource.
- The current and recommended family/generation are identical.
- Medium confidence requires the following conditions:
- The system has less than 10 days of usage data for the resource.
- The current and recommended family/generation are identical.
- Low confidence: The current and recommended family/generation are different.