cloud_chat_agent_metrics does not let you do.
One row is
one availability change
Delivery
Rewritten daily
Columns
18
Where it lands
snapshot_date= partition only, and check for _SUCCESS before you do, as
described in bucket layout.
Columns
bigint
Internal warehouse key. Not stable between deliveries — join on
account_user_availability_histories_id.bigint
Internal warehouse key for the account. Use
account_id.bigint
Internal warehouse key for the agent. Use
account_user_id.varchar(36)
Identifier of the workspace the change belongs to.
varchar(256)
Id of the tenant.
NULL for rows with no tenant mapping.varchar(256)
Name of the tenant.
NULL for rows with no tenant mapping.bigint
Join key. Unique id of the availability change.
varchar(100)
Instance the workspace is served from.
integer
Account the agent belongs to.
bigint
Join key. Agent whose availability changed. Joins to
assigned_agent_id on cloud_chat_conversations.varchar(255)
Name of that agent.
integer
Numeric form of
availability_description.varchar(7)
The state the agent moved to:
online, offline or busy.bigint
Reason the agent picked, when the workspace asks for one.
NULL when it does not.varchar(65535)
That reason as the agent sees it, such as a break or a meeting. Configured per workspace, so the wording is yours.
timestamp
When the agent moved to this state.
timestamp
When the record was last modified.
date
Partition column. Date of the delivery that wrote this file, in
YYYY-MM-DD.