A pipeline is a logical collection of activities that work together to complete a task. A pipeline, for example, could include a set of activities that ingest and clean log data before launching a mapping data flow to analyze the log data.
The pipeline enables users to manage the activities as a group rather than being individual.
- The Run pipeline option available at the top of the section allows users to trigger a Data Factory Pipeline by providing values to the parameters configured using the Azure portal.
Users can view all pipeline runs along with the pipeline activity runs by clicking the pipeline run ID.
Users can also get to know the start time of the activity runs along with its input and output.
- The parameters set when triggering a pipeline will appear in the Parameters column for that pipeline run.
The pipeline runs can be filtered based any one of the following statuses:
- In Progress
Rerun failed pipeline runs
Pipelines can be re-run by using the configured parameters for the respective runs.
A Data Factory Pipeline run might fail due to failure in any of its activities and it occurs quite often in a business orchestration. Serverless360 already facilitates viewing the run history and accessing the details of the failed activity runs. There may be a need to rerun failed activity runs, and Serverless360 allows users to run single or multiple pipeline runs.
Once the re-run operation is complete, a tag that allows users to retrieve the details of the original activity run is added to the child run. The parent pipeline run contains a tag that allows users to view the run history of all its child runs.
Regardless of how many child runs are re-run, only one pipeline run acts as the original activity run for the child runs.
Ignore pipeline run
Pipeline runs can also be ignored in Serverless360. Once ignored, an ignored tag gets associated with the particular run along with the description.
Ignore tag is visible only in Serverless360 and will not have any impact on the actual runs.
Stop pipeline run
- Users can now stop the ongoing pipeline runs by selecting it from the Pipeline Runs tab and clicking the Cancel button.
Action required helps users to focus on the failed pipeline runs. It provides users the privilege to rerun or ignore the failed activity runs.
Any of the pipeline runs used frequently can be marked as a favorite along with an optional description from both Pipeline runs as well as Action Required tabs.
The favorite runs can be re-run, ignored as well as removed from Favorites.
- The list of Integration runtime resources connected to the Data Factory pipeline resource is now displayed in the Overview section.
- In the Overview section, customers can now see a list of triggers associated with a Data Factory pipeline, as well as recurrence data for scheduled triggers.
The Data Factory Pipeline section allows users to quickly re-run failed pipeline runs from the source pipeline that is currently being explored within the specified hours.
The configuration created to run immediately can also be saved for future use in the Automated Tasks section.
Inline task to rerun failed runs
This feature allows users to quickly rerun the pipeline runs that failed within the specified hours (Minimum 1 hour).
Task status can be viewed by navigating to the Automated Tasks section and switching to the Task history tab.
Users can use this feature to quickly create a task that runs immediately.
Navigate to the Automated Tasks section in Serverless360 to create a task with a more detailed configuration, schedule tasks to run at a specific time, or automate the task to run on the specified hours, days, and more.
The failed pipeline runs can be scheduled to run at a specific time from the Automated Task section with options provided to Include previous reruns and Rerun the ignored runs.
The following illustration reruns the failed pipeline runs using Automated task:
Users now have access to a default Data Factory Pipeline Dashboard within the Data Factory Pipeline resource, allowing for enhanced data visualization and tracking of real-time data.
Users are provided with the following pre-defined Dashboard widgets, which can be customized to meet their specific needs.
1. Cancelled Activity Runs
2. Failed Activity Runs vs Succeeded Activity Runs
3. Succeeded Activity Runs
Users can monitor their Data Factory Pipeline resources by configuring the rules available for monitoring.
Navigate to the Monitoring section of the resource to configure the monitoring rules for Data Factory Pipeline.
Users can specify monitoring threshold values based on their needs.
When the monitoring rule type is a metric, selecting metrics against metric rules is also an option.
- The properties of the Data Factory Pipeline can be viewed by clicking on the Properties option.
- The properties are displayed in JSON format as well.