| title | Monitor Azure Data Factory |
|---|---|
| description | Start here to learn how to monitor Azure Data Factory. |
| ms.date | 07/25/2025 |
| ms.subservice | monitoring |
| ms.custom | horz-monitor |
| ms.topic | concept-article |
| author | whhender |
| ms.author | whhender |
[!INCLUDE horz-monitor-intro]
There are several ways to monitor Azure Data Factory.
You can monitor all of your Data Factory pipeline runs natively in Azure Data Factory Studio. To open the monitoring experience, select Launch Studio from your Data Factory page in the Azure portal, and in Azure Data Factory Studio, select Monitor from the left menu.
For more information about monitoring in Azure Data Factory Studio, see the following articles:
- Visually monitor Azure Data Factory
- Data flow monitoring
- Monitor copy activity
- Session log in a Copy activity
You can also monitor Azure Data Factory directly from the Azure portal. Several metrics graphs appear on the Azure portal Overview page for your Data Factory. On the left sidebar menu, you can access the Azure Activity log, or select Alerts, Metrics, Diagnostic settings, or Logs from the Monitoring section.
You can monitor Data Factory pipelines programmatically by using .NET, PowerShell, Python, or the REST API. For more information, see the following articles:
[!INCLUDE horz-monitor-resource-types] For more information about the resource types for Azure Data Factory, see Data Factory monitoring data reference.
[!INCLUDE horz-monitor-data-storage]
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.
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 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] For a list of available metrics for Data Factory, see Data Factory monitoring data reference.
[!INCLUDE horz-monitor-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.
-
To configure diagnostic settings and a Log Analytics workspace to monitor Data Factory, see Configure diagnostic settings and a workspace.
[!INCLUDE horz-monitor-activity-log]
Integration runtime is the compute infrastructure Data Factory uses to provide data integration capabilities across different network environments. Data Factory offers several types of integration runtimes:
- Azure integration runtime
- Self-hosted integration runtime
- Azure-SQL Server Integration Services (SSIS) integration runtime
- Apache Airflow integration runtime
Azure Monitor collects metrics and diagnostics logs for all types of integration runtimes. For detailed instructions on monitoring integration runtimes, see the following articles:
- Monitor an integration runtime in Azure Data Factory
- Monitor an integration runtime within a managed virtual network
- Monitor self-hosted integration runtime in Azure
- Configure self-hosted integration runtime for log analytics collection
- Monitor SSIS operations with Azure Monitor
- Diagnostics logs and metrics for Apache Airflow
[!INCLUDE horz-monitor-analyze-data]
[!INCLUDE horz-monitor-external-tools]
For detailed instructions on configuring diagnostic logs by using the REST API, see Set up diagnostic logs via the Azure Monitor REST API.
[!INCLUDE horz-monitor-kusto-queries]
For example queries, select Logs under Monitoring in the left navigation of your Data Factory page in the Azure portal, and then select the Queries tab. Here are some example queries:
PipelineRuns availability: Gives the availability of the pipeline runs.
ADFPipelineRun
| where Status != 'InProgress' and Status != 'Queued'
| where FailureType != 'UserError'
| summarize availability = 100.00 - (100.00*countif(Status != 'Succeeded') / count()) by bin(TimeGenerated, 1h)), _ResourceId
| order by TimeGenerated asc
| render timechartActivity runs Top 5 failures: Returns top five activities failing with system errors.
ADFActivityRun
| where TimeGenerated >= ago(24h)
| where Status != 'InProgress' and Status != 'Queued'
| where FailureType != 'UserError'
| where ActivityName in (name)
| summarize failureCount = countif(Status != 'Succeeded') by bin(TimeGenerated, 1h), ActivityName
| top 5 by failureCount desc nulls last
| order by TimeGenerated asc
| render timechartPipeline runs latest status: Returns latest status of pipeline runs.
ADFPipelineRun
| summarize argmax(TimeGenerated, * ) by RunId, Status, _ResourceId[!INCLUDE horz-monitor-alerts]
To create and manage alerts, select Alerts under Monitoring in the left navigation of your Data Factory page in the Azure portal.
The following table lists popular alert rules for Data Factory. This is just a recommended list. You can set alerts for any metric, log entry, or activity log entry that's listed in the Data Factory monitoring data reference.
| Alert type | Condition | Description |
|---|---|---|
| Metric | Failed pipeline runs metrics | Whenever the total Failed pipeline runs metrics is greater than 0 |
| Metric | Total entities count | Whenever the maximum Total entities count is greater than 1700000 |
| Metric | Maximum allowed entities count | Whenever the maximum Total factory size (GB unit) is greater than 6 |
Notifications provide proactive alerting during or after execution of a pipeline.
- Send an email with an Azure Data Factory pipeline shows how to configure email notifications from pipeline alerts.
[!INCLUDE horz-monitor-advisor-recommendations]
- See Data Factory monitoring data reference for a reference of the metrics, logs, and other important values created for Data Factory.
- See Monitoring Azure resources with Azure Monitor for general details on monitoring Azure resources.