Supported schemas

The kit reads two Azure Monitor tables. The columns below are the complete set it touches — verified against the published Azure Monitor table reference by a test that parses every shipped query against those schemas.

ApiManagementGatewayLogs

Request identity, status and timing.

Column	Used for
TimeGenerated	Window filter, request time
CorrelationId	Join key; the identity of one logical request
ApiId	Attribution
OperationId	Attribution
ProductId	Attribution depth
ApimSubscriptionId	Export only
UserId	Export only
WorkspaceId	Export only
ResponseCode	Outcome classification
TotalTime	Latency, export only
BackendUrl	Backend identity, export only
_ResourceId	Service identity, export only

ApiManagementGatewayLlmLog

Model, deployment and token counts.

Column	Used for
TimeGenerated	Window filter
CorrelationId	Join key
ModelName	Concentration, candidates
DeploymentName	Concentration
PromptTokens	Input consumption
CompletionTokens	Output consumption
TotalTokens	Total consumption
SequenceNumber	Export only
RequestId	Provider-side request id, export only

This table has no ApiId and no OperationId. The closest thing it carries is OperationName, which is not the operation identity used for attribution. See Architecture.

Never read

RequestMessages, ResponseMessages, RequestBody, ResponseBody.

Prompt and completion content is never touched by any query in the kit. This is enforced by a test over the shipped query files rather than left as a promise in prose.

Four identifiers, never collapsed into one

The export path distinguishes these deliberately, because conflating them produces confident nonsense:

Identifier	What it is
CorrelationId	Azure/APIM correlation — the identity of one logical request
ProviderRequestId	The language model's own request id. Provider-side evidence, not the APIM request
source_group_key	Metergrade's analysis grouping, derived inside Metergrade
ai_workload_id	Confirmed business attribution. Never present in a log