Configure usage connector properties

To include these columns in the usage data output file, in the {connector}.properties file set these properties to "true". Then configure any associated properties, such as name and display name.

By default all quantities are per accounting period, which by default is 1 hour. So for example, a 1 CPU VM running for the full 24 hours of a DAY Accounting period will consume a quantity of 24 CPUs.

Usage data columns	Default	Description

Usage data columns	Default	Description
vm	false	If true, include fee per VM for the account period
vm_on	false	If true, include fee per VM for the account period when the VM was ON
vm_off	false	If true, include fee per VM for the account period when the VM was OFF
cpu	true	If true, include amount of CPU for the account period
cpu_on	false	If true, include amount of CPU for the account period when the VM was ON
cpu_off	false	If true, include amount of CPU for the account period when the VM was OFF
mem	true	If true, include amount of Memory for the account period (MB)
mem_on	false	If true, include amount of Memory for the account period when the VM was ON
mem_off	false	If true, include amount of Memory for the account period when the VM was OFF
ip	true	If true, include amount of IPs used for the account period
vlan	true	If true, include amount of VLANs used for the account period
local_storage	true	If true, include amount of Local Storage used for the account period (GB)
external_storage	true	If true, include amount of External Storage used for the account period (GB)
ha	false	Deprecated. If true include if the VM is hosted on an Abiquo rack with high availability enabled
reserved_server_cpu	false	If true, include amount of CPU in reserved servers that have been explicitly reserved for an Enterprise
reserved_server_memory	false	If true, include amount of RAM in reserved servers that have been explicitly reserved for an Enterprise
repository	false	If true, include the amount of Repository usage (GB) by the enterprise for VM Templates and Instances (conversions are not accounted)
anti_affinity	false	If true, include if the VM is deployed in an anti-affinity layer to ensure it is deployed separately from other VMs in the same layer
firewall	false	If true, include the number of firewalls
loadbalancer	false	If true, include the number of load balancers
hardwareprofile_usage	false	If true, include the amount for hardware profiles used
hardwareprofile_onoff_usage	false	If true, include the amount for hardware profiles used when VMs are ON or OFF
tiered_storage	false	If true, process tiers that are defined in billing.properties file with the storage_tier_<n>_name property Define the storage tiers that you want to include in the output file, in the order that the custom columns should appear
storage_tier_<n>		Define the order of the storage tier in the output file with a number <n> starting from 1
storage_tier_<n>_name		The same case-sensitive name of the 'storage_tier_<n>_name' in the billing.properties file
storage_tier_<n>_display_name		Custom column heading
local_tier_storage	false	If true, process datastore tiers that are defined in billing.properties file with the local_tier_storage_<n>_name property Define the datastore tiers that you want to include in the output file, in the order that the custom columns should appear
local_tier_storage_<n>		Defines the order of the datastore tier in the output file with a number <n> starting from 1
local_tier_storage_<n>_name		The same case-sensitive name as the value of the 'local_tier_storage_<n>_name' in the billing.properties file
storage_tier_<n>_display_name		Custom column heading
backup_usage	false	Process backup pricing per GB usage using the backup_policy_<n> and the backup_policy_<n>_code properties
backup_policy_<n>	false	e.g. backup_policy_2=false
backup_poliy_<n>_code		e.g. backup_policy_2_code=Backup 2
draas_protection_usage	false	If true, process VMs with DRaaS protection
cost_codes	false	If true, process cost codes that are defined in billing.properties file with the cost_code_<n>_name property Define the Cost Codes that you want to include in the output file, in the order you wish those cost codes to appear
cost_code_<n>		Defines the order of the cost code in the output file with a cost code number <n> starting from 1 for the first cost code
cost_code_<n>_name		The same case-sensitive name as the 'cost_code_<n>_name' value in the billing.properties file.
cost_code_<n>_display_name		The customized display names can be values such as strings or account numbers, for example: cost_code_1_display_name = LINUX1 cost_code_2_display_name = WINDOWS10
hypervisors	false	If true, process hypervisor usage Also define the hypervisor usages in the billing.properties file with the hypervisor_<n>_name properties Define the hypervisors that you want to include in the output file, in the order that the custom columns of hypervisors should appear
hypervisor_<n>		Defines the order of the hypervisor in the output file with a hypervisor number <n> starting from 1 for the first hypervisor
hypervisor_<n>_name		E.g. hypervisor_1_name=VMX_04 The same case-sensitive name, which is the same as the value of the 'hypervisor_<n>_name' property in the billing.properties file
hypervisor_<n>_display_name		hypervisor_1_display_name=VMWareESX
custom_<n>		e.g. custom_1=ESXHypervisors If custom=true, set these properties to custom usage names to process the custom usages Also define the custom usage in the billing.properties file with the custom_usage_<n>_name properties Note that the usage number <n> does not need to match the number in the main billing properties file