Product DocumentationAppearance
fact.instance_metering
The fact.instance_metering contains all the information for instance level metering. The data is stored as intervals where events are valid (examples given below). The intervals get updated on every metering run to the latest load date.
A few examples of valid events for any cluster:
- Created > Resumed > Suspended
- Created > Resumed > Dropped
- Altered > Resumed > Suspended
- Altered > Resumed > Dropped
| Column Name | Data Type | Description | Example |
|---|---|---|---|
metering_run | TIMESTAMPTZ | Assigned on each load of the table from the curr_load_ts. | 2023-12-21T05:50:12.650643Z |
datetime_start | TIMESTAMPTZ | The date time when the cluster started. One row is created for each cluster even if the event crosses multiple days. | 2023-12-21T05:31:47Z |
datetime_end | TIMESTAMPTZ | The end time when the cluster is dropped/ suspended/ altered. | 2023-12-21T05:50:12Z |
user_sk | BIGINT NOT NULL | A sequencer generated unique ID for each user. Foreign key to dim.user | 21504 |
cluster_sk | BIGINT NOT NULL | A sequencer generated unique ID for each cluster. Foreign key to dim.cluster pointing to the actual config of the cluster. | 25600 |
hardware_instance_sk | BIGINT NOT NULL | A sequencer generated unique ID for each hardware instance. Foreign key to dim.hardware_instance tracking which hardware instance, the cluster is running on. | 7168 |
vcpu_cores | BIGINT NOT NULL | The number of vCPU provided for each node of the cluster based on hardware instance type. | 16 |
node_count | BIGINT | Number of nodes for the cluster as requested by the user. The user can change the number of nodes by altering the cluster. | 1 |
vcpu_seconds | BIGINT | Total number of vcpu_seconds consumed by the cluster. | 17680 |