Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Table | Categories | Solutions | Supports basic log plan | Queries |
---|---|---|---|---|
ADXCommand Azure Data Explorer command execution summary. |
undefined | LogManagement | No | - |
ADXIngestionBatching Azure Data Explorer ingestion batching operations. These logs have detailed statistics of batches ready for ingestion (duration, batch size and blobs count). |
undefined | LogManagement | No | Yes |
ADXJournal Azure Data Explorer journal (metadata operations). |
resources | LogManagement | No | - |
ADXQuery Azure Data Explorer query execution summary. |
undefined | LogManagement | No | - |
ADXTableDetails Azure Data Explorer table details. |
resources | LogManagement | No | - |
ADXTableUsageStatistics Azure Data Explorer table usage statistics. |
undefined | LogManagement | No | Yes |
AzureActivity Entries from the Azure Activity log that provides insight into any subscription-level or management group level events that have occurred in Azure. |
resources, audit, security | LogManagement | No | Yes |
AzureMetrics Metric data emitted by Azure services that measure their health and performance. |
resources, monitor | LogManagement | Yes | Yes |
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. |
resources | LogManagement | No | Yes |
SucceededIngestion Succeeded ingestion operations logs provide information about successfully completed ingest operations. Logs include data source details that together with |
resources | LogManagement | No | Yes |