This request is to add information about the ITO (Intelligent Throughput Optimization) decision used when processing a copy activity in a fabric pipeline to the JSON output of the copy activity.
This additional run time information would help us understand the cost of running the copy activity.
(This past weekend, we ran into an issue where 100% of our copy activitites tripled in the cost for data movement. Same volumes. Same run times. This issue has since resolved itself but this additional information would have helped us understand what may have changed in the cost calculation.)
dm-p
on:
Allow standard Focus Mode for custom visuals that ...
on:
Data Pipelines - Run only selected activities
on:
More granular control and better design experience...