Microsoft.Kusto/clusters
9 diagnostic categories routing into 9 Log Analytics tables.
Source: Microsoft Learn
Diagnostic categories
-
Command
Ingestion-time transform- Routes to
- ADXCommand
-
DataOperation
Data operation
Cost to export- Routes to
- ADXDataOperation
-
FailedIngestion
Failed ingestion
Ingestion-time transform- Routes to
- FailedIngestion
-
IngestionBatching
Ingestion batching
- Routes to
- ADXIngestionBatching
-
Journal
Ingestion-time transform Cost to export- Routes to
- ADXJournal
-
Query
Ingestion-time transform- Routes to
- ADXQuery
-
SucceededIngestion
Succeeded ingestion
Ingestion-time transform- Routes to
- SucceededIngestion
-
TableDetails
Table details
Ingestion-time transform- Routes to
- ADXTableDetails
-
TableUsageStatistics
Table usage statistics
Ingestion-time transform- Routes to
- ADXTableUsageStatistics
Destination tables
-
ADXCommand
Azure Data Explorer command execution summary.
27 columns in this table.
-
ADXDataOperation
Azure Data Explorer data operation summary.
22 columns in this table.
-
ADXIngestionBatching
Azure Data Explorer ingestion batching operations. These logs have detailed statistics of batches ready for ingestion (duration, batch size and blobs count).
16 columns in this table.
-
ADXJournal
Azure Data Explorer journal (metadata operations).
23 columns in this table.
-
ADXQuery
Azure Data Explorer query execution summary.
44 columns in this table.
-
ADXTableDetails
Azure Data Explorer table details.
27 columns in this table.
-
ADXTableUsageStatistics
Azure Data Explorer table usage statistics.
19 columns in this table.
-
FailedIngestion
Failed ingestion operations logs provide detailed information about failed ingest operations. Logs include data source details, as well as error code and failure status (transient or permanent), that can be used for tracking the process of data source ingestion. Users can identify usage errors (permanent bad requests) and handle retries of transient failures. Ingestion logs are supported for queued ingestion to the ingestion endpoint using SDKs, data connections, and connectors.
21 columns in this table.
-
SucceededIngestion
Succeeded ingestion operations logs provide information about successfully completed ingest operations. Logs include data source details that together with Failed ingestion operations logs can be used for tracking the process of ingestion of each data source. Ingestion logs are supported for queued ingestion to the ingestion endpoint using SDKs, data connections, and connectors.
16 columns in this table.