- Schemas:
METERING_HISTORY view¶
The METERING_HISTORY view in the ACCOUNT_USAGE schema can be used to return the hourly credit usage for an account within the last 365 days (1 year).
Columns¶
Column Name |
Data Type |
Description |
---|---|---|
SERVICE_TYPE |
TEXT |
Type of service that is consuming credits, which can be one of the following:
|
START_TIME |
TIMESTAMP_LTZ |
The date and beginning of the hour (in the local time zone) in which the usage took place. |
END_TIME |
TIMESTAMP_LTZ |
The date and end of the hour (in the local time zone) in which the usage took place. |
ENTITY_ID |
NUMBER |
Internal/system-generated identifier for the service type. |
NAME |
TEXT |
Name of the service type. When the service type is |
CREDITS_USED_COMPUTE |
NUMBER |
Number of credits used by warehouses and serverless compute resources in the hour. |
CREDITS_USED_CLOUD_SERVICES |
NUMBER |
Number of credits used for cloud services in the hour. |
CREDITS_USED |
NUMBER |
Total number of credits used for the account in the hour. This is a sum of CREDITS_USED_COMPUTE and CREDITS_USED_CLOUD_SERVICES. This value does not take into account the adjustment for cloud services, and may therefore be greater than your actual credit consumption. |
BYTES |
NUMBER |
When the service type is |
ROWS |
NUMBER |
When the service type is |
FILES |
NUMBER |
When the service type is |
BUDGET_ID |
TEXT |
The internal identifier for the budget monitoring this credit usage. |
Usage notes¶
Latency for the view may be up to 180 minutes (3 hours), except for the CREDITS_USED_CLOUD_SERVICES column. Latency for CREDITS_USED_CLOUD_SERVICES may be up to 6 hours.
Latency for showing the credit consumption of
SNOWPIPE_STREAMING
may be up to 12 hours.