System usage events are generated by certain activities such as deploying or re-sizing an instance. Periodic events are also generated for all instances that had no activity during an audit period. This means that for each audit period, Cloud Cruiser can reconstruct all activity and allocations in order to compute costs and load data for reporting.
For more information, see http://wiki.openstack.org/SystemUsageData
Usage events include the following:
|
Event
|
Description
|
|
tenant_id
|
Tenant ID that owns this instance.
|
|
user_id
|
User ID that owns this instance.
|
|
instance_id
|
Nova instance ID of this instance.
|
|
instance_type
|
Name of the instance type ('flavor') of this instance.
|
|
instance_type_id
|
Nova ID for instance type ('flavor') of this instance.
|
|
display_name
|
User selected display name for instance.
|
|
created_at
|
Timestamp for when this instance's record was created in Nova.
|
|
launched_at
|
Timestamp for when this instance was last launched by hypervisor.
|
|
image_ref_url
|
Image URL (from Glance) from which this instance was created.
|
|
audit_period_begining
|
Timestamp of beginning of audit period.
|
|
audit_period_ending
|
Timestamp of end of audit period.
|
|
bandwidth
|
Hash listing bandwidth used for each network this instance is connected to. Keys will be network labels, values will be hashes containing the keys 'bw_in', and 'bw_out', listing the incoming, and outgoing bandwidth, respectively, used by that instance, on that network, for that audit period. Bandwidth is reported in bytes.
|
|
state
|
Current state of instance. (such as 'active' or 'deleted').
|
|
state_description
|
Additional human readable description of current state of instance.
|
|
fixed_ips
|
List of IP addresses assigned to instance.
|
|
memory_mb
|
Memory allocation for this instance.
|
|
disk_gb
|
Disk allocation for this instance.
|
