Configure diagnostic settings and a workspace - Azure Data Factory (2024)

FAQs

How do I set diagnostic settings in Azure? ›

In the Azure portal, navigate to your data factory and select Diagnostics on the left navigation pane to see the diagnostics settings. If there are existing settings on the data factory, you see a list of settings already configured. Select Add diagnostic setting.

The Metrics node with the resourceID and MetricAggregation must be included in the diagnostics configuration for your VM if you want to see the VM monitoring data in the Azure portal. The resourceID attribute uniquely identifies the virtual machine in your subscription.

On the existing Azure Cosmos DB account page, select the Features option within the Settings section of the resource menu. Then, select the Diagnostics full-text query feature. In the dialog, select Enable . This setting is applied within a few minutes.

The Azure Diagnostics VM extension enables you to collect monitoring data, such as performance counters and event logs, from your Windows VM. You can granularly specify what data you want to collect and where you want the data to go, such as an Azure Storage account or an Azure Event Hub.

In the Azure portal, search for and select App Services, and then select your app. In the app's left menu, select Configuration > General settings.

The tables used by resource logs depend on what type of collection the resource is using: Azure diagnostics: All data is written to the single AzureDiagnostics table (current / legacy methodology) Resource-specific: Data is written to multiple individual tables for each category of the resource (new methodology)

Diagnostic settings allow you to configure where and how diagnostic data (metrics and logs) from Azure resources is sent. DCRs are part of Azure Monitor and allow you to collect additional data beyond what's automatically captured. And VM Insights provides monitoring and diagnostics specifically for Azure VMs.

The AzureDiagnostics table is a custom log table created exclusively by the Azure Monitor pipeline the first time an Azure resource begins sending logs in Azure Diagnostics mode. Unlike other tables, the AzureDiagnostics table can't be created via an ARM template or tables API.

Diagnostic data isn't permanently stored unless you transfer it to the Microsoft Azure Storage Emulator or to Azure Storage. Once in storage, it can be viewed with one of several available tools.

Which type of data collection requires you to enable diagnostics in Azure? ›

Rationale: You must enable diagnostics to use Azure Monitor to collect event log data. In addition, you must enable diagnostics to collect other information, such as performance counters and crash logs.

Open the menu for a virtual machine in the Azure portal. Select Diagnostic settings in the Monitoring section of the VM menu. Select Enable guest-level monitoring if the diagnostics extension hasn't already been enabled.

To view your diagnostic data, in Log Analytics workspace, open Logs from the left menu. In the query builder, expand LogManagement > AzureDiagnostics. AzureDiagnostics includes Engine and Service events. Notice a query is created on-the-fly.

To enable the diagnostics extension on an existing VM that was created through the classic deployment model, first use the Get-AzureVM cmdlet to get the VM configuration. Then update the VM configuration to include the diagnostics extension by using the Set-AzureVMDiagnosticsExtension cmdlet.