Rightsizing ROI

Rightsizing ROI lets you track Rightsizing recommendations. You can also as create, work with, and review issues, and request tickets based on the recommendations.

With Rightsizing ROI, you can configure policies to automatically create issues and requests when tracking recommendations. You can also use Rightsizing ROI to accurately show realized savings from actioning these resource optimization recommendations.

Rightsizing ROI functionality has three support options:

• A Jira Cloud integration using the Jira Service Management extension that can automatically create Jira issues and requests, and use bi-directional synchronization of Jira ticket status to keep your projects in sync.
• A ServiceNow integration using a Cloudability generated script that can automatically create ServiceNow incidents and requests, and also uses bi-directional synchronization of ServiceNow ticket status to keep your projects in sync.
• Stand-alone tracking functionality that is wholly contained within Cloudability itself and requires no third-party integration.

Jira integration

• Configure Jira Cloud in Cloudability.
• Learn about Jira Integration - Setup

ServiceNow integration

Learn about ServiceNow Integration - Setup

To get your recommendations:

1. Configure a policy.
2. Triage your issues and requests (Jira or ServiceNow integration).
3. View recommendations on the Rightsizing dashboard.

To configure a policy:

1. Navigate to Settings > Rightsizing Policies .
2. Select the Add a Policy button. The Create a Policy drawer opens.
3. Enter your policy criteria:
   • Name: Enter a name for your policy.
   • 30 Day Savings Threshold: Enter the minimum cost savings your require across 30 days.
   • Cloud Service: Select the Cloud resource you want to include.
   • Cost Basis: Choose the cost basis to use when calculating the threshold.
   • Actions: Check the boxes to include rightsizing actions.
   • Maximum Results: Enter the maximum results added from each scheduled run.
   • View: Select the filter for your resources.
   • Integration Type: Select the type of ROI integration for this policy.
   • Project: For Jira, select the project where the created tickets are displayed.
   • Task: For ServiceNow, select the task type where created tickets are displayed.
   • Request Type: For Jira, select the issue type (Jira) or request type (Jira Service Management).
   • Schedule: Select the recurrence.
   • Days of the week: If the policy runs weekly, select the day you want it to run.
   • End After: Choose the policy end date.
4. Select the Create button to create the policy, or select the Create and Run button to both create a policy and run it.

To enable the automatic creation of tickets, you need to create and configure a policy.

The issue, request, or incident tickets created by the policy are displayed in your designated Jira or ServiceNow ticket location.

Each ticket contains:

• An overview of the recommendation.
• A link to the details of the recommendation in Cloudability.
• Labels from the key resource attributes.

In Cloudability, tickets created by the policy are displayed in the Rightsizing ROI dashboard. It displays the following aggregated key performance indicators (KPIs):

• Potential Savings: Potential saving opportunities from all unresolved tickets.
• Realized Savings: Realized savings for all resolved tickets for the next 30 days.

Individual tickets

The Rightsizing dashboard also displays the details of each ticket created by your policy:

• Cloud Service: The Cloud provider and service.
• Resource Name: The name of the Cloud resource.
• Resource ID: A unique identifier for a specific AWS resource.
• Ticket: The ticket associated with this resource.
• Type: Either Jira, ServiceNow, or Cloudability.
• Status: The current status of the ticket.
• Assigned To: The ticket owner.
• Created: The date the ticket was created.
• Closed : The date the ticket was resolved or "N/A" if the ticket is still active.
• Resolution: The resolution status of the ticket.
• Potential Savings: Potential savings for the ticket identified by the recommendation.
• Realized Savings: Realized savings based on the new instance type.
• Details : The details of the recommendation.

How long will the realized savings appear in the rightsizing ROI? Does it disappear or stay there forever?

Realized savings data in the Rightsizing ROI feature doesn't get deleted; it remains in Cloudability forever. It is a historical record of the change that was made and the money that was saved.

How are realized savings calculated?

At the time the recommendation is first tracked, Cloudability stores information about the resource in its current state. When a change to the resource occurs, the amount of savings realized is calculated based on the 30-day costs from the original resource state minus the 30-day costs from the new resource state. Since future use is unknown, the realized savings value is calculated as (current-resource-type * rate * 24 hrs * 30 days) - (previous-resource-type * rate * 24 hrs * 30 days) as an estimation of usage. The value for realized savings reflects the change that was actually made and is not directly influenced by what may have been recommended.

What is the maximum number of polices that can be created?

Up to 30 policies. However, if you use a third-party integration (like Jira Cloud or Service Now), you may be able to circumvent this limit by using those services to triage the tickets and requests based on the resource information provided. For example, resource tags are included in the tickets created.

What is the maximum number of tickets that can be created per policy run?

Up to 100 tickets per run. However the limit is constrained by the number of open tickets. An "open" ticket is currently defined as any ticket that does not have a "realized savings" value.