- Schema:
SNOWPIPE_ STREAMING_ CLIENT_ HISTORY view¶
This Account Usage view can be used to query the events recorded for Snowpipe Streaming clients within the last 365 days (1 year). Each row is a single client event, such as BLOB_PERSIST, with the time the event occurred and the size of the blob. The view doesn’t record durations. It covers your entire Snowflake account.
Columns¶
| Column Name | Data Type | Description |
|---|---|---|
| CLIENT_NAME | VARCHAR | Name of the Snowpipe Streaming ingest client. |
| SNOWFLAKE_PROVIDED_ID | VARCHAR | Internal/system-generated identifier for the Snowpipe Streaming ingest client used for the data load. |
| EVENT_TIMESTAMP | TIMESTAMP_LTZ | Time (in the local time zone) at which the event occurred. |
| EVENT_TYPE | VARCHAR | Type of the event. |
| BLOB_SIZE_BYTES | NUMBER | The blob size in bytes. |
Usage notes¶
- Latency for the view may be up to 120 minutes (2 hours).
- Each row is a single event and has no end time or elapsed duration. For billing, each distinct second that has one or more events counts as one client-second.
Examples¶
Query the Snowpipe Streaming client events recorded within the last 365 days.
The query returns the following results.
Query the hourly credits consumed by each client loading data into Snowflake tables using Snowpipe Streaming within the last 365 days.
The query uses COUNT(DISTINCT event_timestamp) because there can be multiple events per second. Each distinct second counts once, regardless of the number of events in that second.