Skip to main content

View and apply recommendations


After you enable CCM, it may take up to 48 hours for the recommendations to appear in Cloud Costs. It depends on the time at which CCM receives the utilization data for the service. In Cloud Costs, go to the Recommendations page.

Before you begin

To know how these recommendations are computed, see the following topics:

View recommendations

The Recommendations page displays the following information:

  • A breakdown of all the available recommendations.
  • Potential Monthly Savings across your ECS clusters if you apply the recommendations.
  • Forecasted Monthly Spend across your ECS clusters if you do not apply the recommendations.

If you do not want to view the recommendations for the child resources such as Workloads, deselect the Child Resources checkbox in the Include dropdown list at the top of the page.

The Recommendation Breakdown displays the following information:

Column nameDescription
Resource NameName of the resource for which CCM displays the recommendation.
Monthly SavingsPotential monthly savings for your resource, if you apply the recommendations.
Potential Monthly SpendThe monthly cost of the recommendation.
Recommendation ActionThe intended action by applying the recommendation. For example, rightsizing or resizing. Based on the available metrics, CCM recommends rightsizing or resizing your CPU, memory, or node counts.
Ticket StatusThe status of the Jira or ServiceNow ticket. If the ticket is yet to be created, a link to create a ticket is displayed.

Ignore list

You can ignore a recommendation for your node pool or workload. Select the More actions icon (three vertical dots), and then select Add Nodepool to Ignore list or Add Workload to Ignore list.

To remove a recommendation from the ignore list, select Manage Ignore List. Then, select Remove.

Apply recommendations

To apply recommendations, you need to raise a ticket in the ticketing tool that your organization uses. To configure the ticketing tool setup, perform the following steps:

  1. Navigate to Cloud Costs > Setup > Default Settings.
  2. Expand Cloud Cost Management.
  3. Under Ticketing preferences, select the Ticketing tool and the Ticketing tool connector. If you do not have an existing connector, create a new one.

The default ticketing tool is Jira. You can choose ServiceNow if that's the tool used in your organization. 4. Select Save.


Switching your ticketing tool between Jira and ServiceNow results in the removal of the existing recommendation tickets. The status of the tickets changes to Create a ticket.

Go to the Recommendations page and create tickets to apply recommendations.

Perform the following steps to raise a ticket to apply recommendations:

  1. Select Create a ticket. In case you haven't set up your ticketing tool settings on the account level, you will see a prompt guiding you to access the Default Settings page to configure both the ticketing tool and the associated connector.

  2. Enter the following ticket details:

  • Jira project — Select the Jira project where you want to create a ticket. Go to Create Jira Issues in CD Stages.
  • Issue type — Select a Jira issue type from the list of types in the Jira project you selected. Go to Create Jira Issues in CD Stages.
  • Ticket summary — Add a summary of the issue.
  • Description — Add a description for the issue.

The ticket is created. The status of the ticket changes to To do. You need to assign the ticket to apply the recommendations. After applying the recommendations, when the ticket status changes to Done, the recommendation is displayed in the Applied Recommendations tab. If you have not changed the ticket status to Done after applying the recommendation, you could use the More actions icon (three vertical dots), and then select Mark as applied to move the recommendation to the Applied Recommendations tab. To view the recommendations that are applied, and the cost savings realized, select the Applied Recommendations tab.

Create a Jira or ServiceNow connector

  1. In the Overview step, enter the name.
  2. Optionally, enter a short description and tags.
  3. In the Details step, enter the base URL. For example, For more information, go to Configuring the base URL.
  4. Enter the email ID used to log in to your Jira account.
  5. Create or select a Harness encrypted test secret for the API key. To create a secret, go to Add and reference text secrets.
  6. In the Delegates Setup step, select one of the following options:
    • Use any available Delegate: Select this option to let Harness choose a Delegate at runtime. When a task is ready to be assigned, the Harness Manager first validates its lists of Delegates to assign the task. The following information describes how the Harness Manager validates and assigns tasks to a Delegate:

      • Heartbeats: Running Delegates send heartbeats to the Harness Manager in one-minute intervals. If the Manager does not have a heartbeat for a Delegate when a task is ready to be assigned, it will not assign the task to that Delegate.

      • Tags: Go to Use delegate selectors.

      • Allowlisting: After a Delegate is validated for a task, it is allowlisted for that task. This Delegate is likely to be used again for that task. The allowlisting criteria is the URL associated with the task, such as a connection to a cloud platform, repo, or API. A Delegate is allowlisted for all tasks using that URL. The Time-To-Live (TTL) for the allowlisting is 6 hours, and the TTL is reset with each successful task validation.

      • Blocklisting: If a Delegate fails to perform a task, it is blocklisted for that task. This Delegate is not selected again to perform that task. TTL is five minutes. This is true even if there is only one Delegate and the Delegate is selected for that task with a Selector.

    • Only use Delegates with all the following tags: Select this option to use specific Delegates using their Tags. You only need to select one of a Delegate's Tags to select it. All Delegates with the Tag are selected. This option is useful when you have installed specific software on specific Delegates and want to ensure that your Pipeline uses those Delegates.

  7. Select Save and Continue. The Connector is created and validated.

You can create and use filters to select resources and recommendations.

You can filter by:

  • Resource Name — The name of the resource being monitored.
  • Namespace — A namespace in the cluster.
  • Cluster Name — A cluster in your infrastructure.
  • Resource Type — The type of resources for which the recommendation is displayed. Currently, CCM supports ECS service, node pool, and workload.
  • Savings — Enter the minimum monthly savings. For example, all the recommendations with potential monthly savings of more than $1000.
  • Potential Spend — Filter by forecasted monthly spend greater than the specified amount. For example, all the recommendations with forecasted monthly spend of more than $1000.

The recommendation for the selected resource is displayed.

Select a recommendation to view its details.

Within a recommendation, select the number of days to compute recommendations based on the utilization data. You can select the last day, 7 days, or 30 days.

You can use this information to optimize your resources to potentially reduce your monthly cloud costs.

Export recommendations data

You can export your Recommendations as comma-separated values (CSV) files. Exporting allows you to use the data in other software. Export respects the filters applied by the user in the filter panel.


  • Only comma-separated values files (CSV) are supported.
  • The maximum number of rows allowed in one export is 10,000 rows.
  • The more rows you export, the slower the export will be.

Create a Recommendations Export

  1. Open Recommendations.

2. Click Export CSV.

  1. Enter a name for the CSV file.

  2. In Export rows up to, enter the number of rows you want exported. The number of rows should be greater than or equal to 1.

  3. Click Download. The file is downloaded to your computer.