changes

Author: v-thepet

articles/data-factory/.openpublishing.redirection.data-factory.json

@@ -1081,11 +1081,6 @@
             "redirect_url": "/azure/data-factory/monitor-data-factory",
             "redirect_document_id": false
           },
-          {
-            "source_path_from_root": "/articles/data-factory/monitor-configure-diagnostics.md",
-            "redirect_url": "/azure/data-factory/monitor-data-factory",
-            "redirect_document_id": false
-          },
           {
             "source_path_from_root": "/articles/data-factory/connector-troubleshoot-google-adwords.md",
             "redirect_url": "/azure/data-factory/connector-troubleshoot-google-ads",

articles/data-factory/TOC.yml

@@ -900,6 +900,8 @@ items:
       items:
       - name: Monitor
         href: monitor-data-factory.md
+      - name: Configure diagnostics settings and workspace
+        href: monitor-configure-diagnostics.md
       - name: Set up diagnostics logs via the Azure Monitor REST API
         href: monitor-logs-rest.md
       - name: Monitor SSIS operations with Azure Monitor

articles/data-factory/monitor-configure-diagnostics.md

@@ -0,0 +1,54 @@
+---
+title: Configure diagnostic settings and a workspace
+description: Learn how to configure diagnostic settings and a Log Analytics workspace to monitor Azure Data Factory.
+author: ukchrist
+ms.author: ulrichchrist
+ms.reviewer: jburchel
+ms.service: data-factory
+ms.subservice: monitoring
+ms.topic: conceptual
+ms.date: 07/20/2023
+---
+
+# Configure diagnostic settings and a workspace
+
+Create or add diagnostic settings for your data factory.
+
+1. 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**.
+
+   :::image type="content" source="media/data-factory-monitor-oms/add-diagnostic-setting.png" alt-text="Screenshot that shows adding a diagnostic setting if settings exist.":::
+
+1. Give your setting a name, select **Send to Log Analytics**, and then select a workspace from **Log Analytics workspace**.
+
+    * In _Azure-Diagnostics_ mode, diagnostic logs flow into the _AzureDiagnostics_ table.
+    * In _Resource-Specific_ mode, diagnostic logs from Azure Data Factory flow into the following tables:
+      - _ADFActivityRun_
+      - _ADFPipelineRun_
+      - _ADFTriggerRun_
+      - _ADFSSISIntegrationRuntimeLogs_
+      - _ADFSSISPackageEventMessageContext_
+      - _ADFSSISPackageEventMessages_
+      - _ADFSSISPackageExecutableStatistics_
+      - _ADFSSISPackageExecutionComponentPhases_
+      - _ADFSSISPackageExecutionDataStatistics_
+
+      You can select various logs relevant to your workloads to send to Log Analytics tables. For example: 
+        - If you don't use SQL Server Integration Services (SSIS) at all, you don't need to select any SSIS logs. 
+        - If you want to log SSIS integration runtime (IR) start, stop, or maintenance operations, select SSIS IR logs. 
+        - If you invoke SSIS package executions via T-SQL on SQL Server Management Studio, SQL Server Agent, or other designated tools, select SSIS package logs. 
+        - If you invoke SSIS package executions via Execute SSIS Package activities in Data Factory pipelines, select all logs.
+
+    * If you select _AllMetrics_, various Data Factory metrics are made available for you to monitor or raise alerts on. These metrics include the metrics for Data Factory activity, pipeline, and trigger runs, and for SSIS IR operations and SSIS package executions.
+
+   :::image type="content" source="media/data-factory-monitor-oms/monitor-oms-image2.png" alt-text="Screenshot that shows naming your settings and selecting a Log Analytics workspace.":::
+
+    > [!NOTE]
+    > Because an Azure log table can't have more than 500 columns, we *highly recommend* that you select _Resource-Specific mode_. For more information, see [Azure diagnostics logs reference](/azure/azure-monitor/reference/tables/azurediagnostics).
+
+1. Select **Save**.
+
+After a few moments, the new setting appears in your list of settings for this data factory. Diagnostic logs are streamed to that workspace as soon as new event data is generated. Up to 15 minutes might elapse between when an event is emitted and when it appears in Log Analytics.
+
+## Related content
+
+[Set up diagnostics logs via the Azure Monitor REST API](monitor-logs-rest.md)

articles/data-factory/monitor-data-factory.md

@@ -1,7 +1,7 @@
 ---
 title: Monitor Azure Data Factory
 description: Start here to learn how to monitor Azure Data Factory.
-ms.date: 02/26/2024
+ms.date: 02/28/2024
 ms.custom: horz-monitor
 ms.topic: conceptual
 author: jonburchel
@@ -44,22 +44,22 @@ For more information about the resource types for Azure Data Factory, see [Data
 
 [!INCLUDE [horz-monitor-data-storage](~/articles/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-data-storage.md)]
 
-### Store Data Factory metrics and pipeline run data
+### Store Data Factory pipeline run data
 
-Data Factory stores pipeline run data for only 45 days. Use Azure Monitor to route diagnostic logs if you want to keep the data for a longer time.
+Data Factory stores pipeline run data for only 45 days. Use Azure Monitor to route diagnostic logs if you want to keep the data longer.
 
-- **Storage account**: Save your diagnostic logs to a storage account for auditing or manual inspection. You can use diagnostic settings to specify the retention time in days.
-- **Event hub**: Stream the logs to Azure Event Hubs to become input to a partner service or custom analytics solution like Power BI.
-- **Log Analytics**: Analyze the logs with Log Analytics if you want to write complex queries, create custom alerts, or monitor across data factories.
-- **Partner solutions:** Send diagnostic logs to partner solutions through integration.
+Route data to Log Analytics if you want to analyze it with complex queries, create custom alerts, or monitor across data factories. You can route data from multiple data factories to a single Log Analytics workspace.
 
- You can route data from multiple data factories to a single Log Analytics workspace. You can also use a storage account or event hub namespace that isn't in the subscription of the resource that emits logs. The user who configures the setting must have appropriate Azure role-based access control (Azure RBAC) access to both subscriptions.
+You can use a storage account or event hub namespace that isn't in the subscription of the resource that emits logs. The user who configures the setting must have appropriate Azure role-based access control (Azure RBAC) access to both subscriptions.
 
 [!INCLUDE [horz-monitor-platform-metrics](~/articles/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-platform-metrics.md)]
 For a list of available metrics for Data Factory, see [Data Factory monitoring data reference](monitor-data-factory-reference.md#metrics).
 
 [!INCLUDE [horz-monitor-resource-logs](~/articles/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-resource-logs.md)]
-For the available resource log categories, their associated Log Analytics tables, and the logs schemas for Data Factory, see [Data Factory monitoring data reference](monitor-data-factory-reference.md#resource-logs).
+
+- For the available Data Factory resource log categories, their associated Log Analytics tables, and the logs schemas, see [Data Factory monitoring data reference](monitor-data-factory-reference.md#resource-logs).
+
+- To configure diagnostic settings and a Log Analytics workspace to monitor Data Factory, see [Configure diagnostic settings and a workspace](monitor-configure-diagnostics.md).
 
 [!INCLUDE [horz-monitor-activity-log](~/articles/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-activity-log.md)]