Skip to content

Commit a8d490b

Browse files
authored
Update concepts-data-flow-monitoring.md
1 parent 62907f0 commit a8d490b

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/data-factory/concepts-data-flow-monitoring.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.reviewer: douglasl
77
ms.service: data-factory
88
ms.topic: conceptual
99
ms.custom: seo-lt-2019
10-
ms.date: 10/07/2019
10+
ms.date: 04/17/2020
1111
---
1212

1313
# Monitor Data Flows
@@ -28,6 +28,10 @@ When you are in the graphical node monitoring view, you will see a simplified vi
2828

2929
![Data Flow Monitoring](media/data-flow/mon003.png "Data Flow Monitoring")
3030

31+
Here is a video overview of monitoring performance of your data flows from the ADF monitoring screen:
32+
33+
> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4u4mH]
34+
3135
## View Data Flow Execution Plans
3236

3337
When your Data Flow is executed in Spark, Azure Data Factory determines optimal code paths based on the entirety of your data flow. Additionally, the execution paths may occur on different scale-out nodes and data partitions. Therefore, the monitoring graph represents the design of your flow, taking into account the execution path of your transformations. When you click on individual nodes, you will see "groupings" that represent code that was executed together on the cluster. The timings and counts that you see represent those groups as opposed to the individual steps in your design.

0 commit comments

Comments
 (0)