In this topic:
Estimated and actual costs
vCommander calculates the estimated cost of a service on an annual basis by adding the storage costs, operating system costs, support costs and custom attribute costs to the cost of the allocated or reserved resources for the service. To learn how to edit the costs that vCommander uses in its calculations, see Configuring Cost Models.
Actual costs are displayed only for AWS and Azure services and are taken directly from historical billing data. Actual costs include prepaid amounts, overages, promotions and adjustments. Business support and taxes are shown on the first day of the month and aren't calculated per VM. To learn how to retrieve billing data, see Retrieving AWS Billing Data and Retrieving Azure Billing Data.
Actual costs are not shown for GCP instances. Google charges aggregated CPU and memory usage costs, grouped by project and service type; GCP billing data doesn't include costs for individual VMs.
Viewing estimated and actual costs
Views menu > Operational or Deployed
Any level of Access Rights
The cost of a service is displayed on the Details pane of the service's Summary tab.
By default, Estimated Costs are shown, but you can also display the Actual Costs. To learn how to display the Actual Costs property in the Details pane, see Displaying properties.
In the Details pane, click the blue Details link next to Estimated Costs or Actual Costs to open the Costs Details dialog.
Use the drop-down lists to select either Estimated Costs or Actual Costs, and select the time period.
Because deployment decisions (for example, target host or cluster and storage location) can affect the total cost of a service when it's deployed, the cost of a service in the Service Catalog may not match that displayed for the source service in the tree. The Estimated Cost displayed in the Details pane for a VM template includes only storage and custom attribute costs; it doesn't include CPU, memory or operating system costs. The cost displayed for that same template when added to the Service Catalog, however, includes all resource costs. The Service Catalog cost provides you with a more realistic view of what the template would cost when deployed as a VM.
Also note that the Service Catalog costs displayed in vCommander are not necessarily (or even likely to be) what the Service Portal user will see. In the Service Portal, service catalog costs are based on the provisioning destinations assigned to the user. If multiple destinations are assigned, or no destination is available, vCommander displays the most reasonable cost estimate. If a Service Portal users chooses the destination on the request form, the displayed costs change accordingly.
To learn how costs are displayed for AWS stacks, see Managing AWS CloudFormation Templates and Stacks with vCommander. To learn how costs are displayed for ARM templates, see Managing ARM Templates and Resource Groups with vCommander. Note that the cost of a public Azure image is always displayed as $0.
Azure costs don't include taxes.