Schema:

ORGANIZATION_USAGE

For guidance on query performance when using organization-wide usage views, see Performance (Organization Usage).

SNOWPARK_CONTAINER_SERVICES_HISTORY view

Important

This view is only available in the organization account. For more information, see Premium views in the organization account.

Organization Usage performance

When you query a specific view in the SNOWFLAKE.ORGANIZATION_USAGE schema, follow the organization-wide guidance in Performance (Organization Usage): bound every scan on history views, list columns explicitly, and use the time filter column table plus worked SQL and anti-patterns there.

This Organization Usage view can be used to query the hourly compute pool credit usage across all the accounts in your organization.

See also:

SNOWPARK_CONTAINER_SERVICES_HISTORY view (Account Usage)

Columns

Organization-level columns

Column NameData TypeDescription
ORGANIZATION_NAMEVARCHARName of the organization.
ACCOUNT_LOCATORVARCHARSystem-generated identifier for the account.
ACCOUNT_NAMEVARCHARUser-defined identifier for the account.

Additional columns

Column NameData TypeDescription
START_TIMETIMESTAMP_LTZThe date and beginning of the hour (in the local time zone) in which the usage took place.
END_TIMETIMESTAMP_LTZThe date and end of the hour (in the local time zone) in which the usage took place.
COMPUTE_POOL_NAMEVARCHARName of the compute pool which incurred the credit usage.
COMPUTE_POOL_IDNUMBERInternal, Snowflake-generated identifier of the compute pool which incurred the credit usage.
IS_EXCLUSIVEBOOLEANTRUE, if the compute pool was created for an application.
APPLICATION_NAMEVARCHARThe name of the application for which the compute pool was created. NULL if the compute pool was not created for an application or if the application no longer exists.
APPLICATION_IDNUMBERThe ID of the application for which the compute pool was created; otherwise NULL.
CREDITS_USEDNUMBERNumber of credits the compute pool used in the hour.

Usage notes

  • Latency for the view may be up to 24 hours.
  • The credit rate usage is determined based on the machine type (instance family) of the compute pool, as outlined in the consumption table.
  • Rows are only included for hours in which a compute pool consumed credits.