Every customer has their own contracts and this means that the costs associated with cloud compute and DBUs may differ between customers. To ensure the costs in Overwatch are as accurate as possible it’s important that these costs are configured as accurately as possible.
There are three essential components to the cost function:
The DBU contract costs are captured from the Overwatch Configuration maintained as a slow-changing-dimension in the dbuCostDetails table. The compute costs and dbu to node associations are maintained as a slow-changing-dimension in the instanceDetails table.
To customize costs configure and complete your first Bronze run. Before running Silver/Gold, alter the instanceDetails table to your satisfaction. Note that this is only true for instanceDetails not dbuCostDetails as Overwatch will maintain this table for you.
Note that each subsequent workspace referencing the same dataTarget will append default compute prices to instanceDetails
table if no data is present for that organization_id (i.e. workspace).
If you would like to customize compute costs for all workspaces,
export the instanceDetails dataset to external editor (after first init), add the required metrics referenced above for each workspace, and update the target table with the customized cost information. Note that the instanceDetails object in the consumer database is just a view so you must edit/overwrite the underlying table in the ETL database. The view will automatically be recreated upon first pipeline run.
IMPORTANT These cost lookup tables are slow-changing-dimensions and thus they have specific rule requirements; familiarize yourself with the details at the links below. If the rules fail, the Gold Pipeline will fail with specific costing errors to help you resolve it.
Helpful Tool (AZURE_Only) to get pricing by region by node.
Sample compute details available below. These are only meant for reference, they do not have all required fields. Follow the instruction above for how to implement custom costs. AWS Example | Azure Example
Overwatch is not able to determine the VM SKU provided by your cloud provider (i.e. OnDemand/Spot/Reserved); thus the exact price of compute asset at the time of provisioning isn’t available. The compute_contract_price configured in instanceDetails is best configured as the average price you received over some previous period to allow Overwatch to best estimate the compute costs; nonetheless, the compute costs are just that, estimates.