Merge pull request #90301 from chez-charlie/release-branch-1

Update ADF Azure Monitor Log Analytics Doc

Author: PRMerger10

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

@@ -462,6 +462,9 @@ Create or add diagnostic settings for your data factory.
 
 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.
 
+* In _Resource-Specific_ mode, diagnostic logs from Azure Data Factory flow into _ADFPipelineRun_, _ADFTriggerRun_, and _ADFActivityRun_ tables
+* In _Azure-Diagnostics_ mode, diagnostic logs flow into _AzureDiagnostics_ table
+
 > [!NOTE]
 > Because an Azure log table can't have more than 500 columns, we highly recommended you select Resource-Specific mode. For more information, see [Log Analytics Known Limitations](https://docs.microsoft.com/azure/azure-monitor/platform/diagnostic-logs-stream-log-store#known-limitation-column-limit-in-azurediagnostics).
 
@@ -503,6 +506,9 @@ You can visualize the preceding metrics, look at the queries behind these metric
 
 ![Graphical representation of pipeline runs by data factory"](media/data-factory-monitor-oms/monitor-oms-image8.png)
 
+> [!NOTE]
+> Azure Data Factory Analytics (Preview) sends diagnostic logs to _Resource-specific_ destination tables. You can write queries against the following tables: _ADFPipelineRun_, _ADFTriggerRun_, and _ADFActivityRun_.
+
 ## Alerts
 
 Sign in to the Azure portal and select **Monitor** > **Alerts** to create alerts.