Question 790
A Blob service diagnostic setting is already successfully sending resource logs to Log Analytics in resource-specific table mode. A test read appears in the workspace, but an analyst queries only AzureDiagnostics and mistakenly reports that no Blob access audit events were ingested. Which specific query correction addresses the problem?
Explanation
Correct Answer
Microsoft defines StorageBlobLogs as the Blob service resource-specific Log Analytics table, with TimeGenerated, OperationName, StatusCode and other request fields. Query that table when the diagnostic collection mode is resource-specific; an empty AzureDiagnostics query alone does not show that ingestion failed.
Incorrect Answers
AzureDiagnostics is not the only supported resource-log destination table. Recreating a working storage account would be destructive and would not solve a query aimed at the wrong table.
The Activity Log concerns Azure Resource Manager control-plane events, not a full request-by-request Blob service data-plane audit stream. It cannot substitute for the already-ingested Blob resource logs.
Platform metrics are distinct from resource log records. Turning off diagnostic logging would stop future Blob audit ingestion instead of fixing the analyst's table selection.