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.
Microsoft Discovery application logs are stored in a dedicated Log Analytics workspace inside the Managed Resource Group (MRG) that Azure provisions for each Discovery resource. This article explains how to navigate to the MRG and open the Log Analytics workspace for a workspace, supercomputer, or bookshelf.
Note
This article covers access to application logs in MRG-based Log Analytics workspaces. For control plane audit logs, see View activity logs for Microsoft Discovery resources. For configuring log export to a storage account, see Enable audit logging for Microsoft Discovery resources.
Prerequisites
- An Azure account with access to an active subscription containing Microsoft Discovery resources.
- Reader role (or higher) on the Discovery resource and its associated Managed Resource Group.
- Permission to query the Log Analytics workspace and its tables, such as Log Analytics Reader at the workspace scope. Resource visibility alone doesn't establish query access. See Manage access to Log Analytics workspaces.
Navigate to the Managed Resource Group
Each Microsoft Discovery resource—workspace, supercomputer, or bookshelf—has an associated MRG that contains its managed infrastructure, including the Log Analytics workspace. Use the steps below to locate the MRG for the resource you want to investigate.
- In the Azure portal, search for Microsoft Discovery or navigate to All resources.
- Select the workspace you want to troubleshoot.
- On the workspace overview page, locate the Managed Resource Group field. It appears under the Essentials section.
- Select the link to open the Managed Resource Group.
Open the Log Analytics workspace
After you navigate to the MRG:
- In the MRG resource list, locate the resource of type Log Analytics workspace.
- Select it to open the workspace.
- In the left navigation pane, select Logs.
- If a query dialog appears, close it to access the full Logs query editor.
You're now in the Log Analytics Logs interface for that Discovery resource.
Explore available tables
To see the log tables available for the resource:
- In the left panel of the Logs interface, select the Tables tab.
- Search for the table name, or expand Custom Logs for Discovery custom tables such as
DiscoveryLogs_CL,KubeEvents_CL, orDiscoveryBookshelfLogs_CL. - For bookshelf AI Search diagnostics, look for
AzureDiagnosticsrather thanDiscoveryLogs_CL. It isn't a Discovery custom table.
Tip
You can select any table name to run a default query that fetches the most recent entries, which is useful for quickly confirming that logs are being ingested.
Adjust the time range
Set the time range by using the selector at the top of the query editor. You can further filter rows by using where TimeGenerated in your KQL query. For Basic or Auxiliary tables, the query requires an explicit time range in the picker or API timespan; a KQL time filter doesn't replace it. See Query Basic and Auxiliary tables.
DiscoveryLogs_CL
| where TimeGenerated > ago(1h)
| order by TimeGenerated desc
Replace ago(1h) with ago(7d) to filter to the last seven days, within the selected query time range and available table retention.
Next steps
Now that you can access the Log Analytics workspace, query logs for your specific resource: