ResourceUtilization

When the Persistent Query Controller uses automated server selection, every Remote Query Dispatcher's usage is tracked. All changes in the dispatchers' resource utilization are logged in the ResourceUtilization table. This includes:

When the controller starts a Persistent Query, the updated resource utilization of the dispatcher running the query is logged with an Internal notification comment.
When a dispatcher notifies the controller that its resource utilization has changed, the updated resource utilization is logged with a Dispatcher notification comment.
When the controller establishes a connection to a dispatcher, an Initial dispatcher connection event is logged.
When the controller loses its connection to a dispatcher, the dispatcher's last known resource utilization is logged with a Lost dispatcher connection comment.
Discrepancies between the controller's view of a dispatcher's resource utilization and the dispatcher's self-reported resource utilization are logged with a Did not receive dispatcher notification comment.

Columns

Column Name	Column Type	Description
`Date`	String	The date on which the state change occurred. This is the partitioning column.
`Timestamp`	DateTime	The timestamp of the event.
`LoggingProcessName`	String	The process logging the event (usually `PersistentQueryController`).
`ResourceProcessName`	String	The process name of the resource being tracked; this will be the dispatcher name.
`HeapUsageMB`	int	The dispatcher's current heap utilization in MB.
`HeapAvailableMB`	int	The dispatcher's current heap availability in MB.
`WorkerCount`	int	The dispatcher's current worker count.
`Comment`	String	A comment explaining the reason for the update, including a description of the worker where available.