Overview

You can access the Pipeline Wall from the SnapLogic Dashboard. The Pipeline Wall enables you to view details of all the Pipelines executed within the Org. Organized into two sections, the Pipeline Wall separates all executing Pipelines from those that have completed execution. For each Pipeline, the Pipeline Wall shows you a series of details, such as the Pipeline name, the username of the user who executed it, and the Snaplex and node in which the Pipeline was executed.

Additionally, you can also check execution statistics for a Pipeline, view run logs associated with it, and search for a Pipeline using its name, the username, Snaplex, and values of Pipeline and error Pipeline parameters. 

Description

The Pipeline Wall comprises two sections:

• Executing Pipelines. Displays all Pipelines that are either queued to execute or being executed.

• Pipeline Execution History. Displays all Pipelines that either completed execution (successfully or with errors) or were stopped manually.

By default, the sections are titled Executing Pipelines of My Executions and Pipeline Execution History of My Executions.

For Org admins, the sections are titled Executing Pipelines of All Projects and Pipeline Execution History of All Projects.

The section titles also change depending on the selected value of Show Only. For example, if shared is selected, the titles would read Executing Pipelines of shared and Pipeline Execution History of shared, respectively.

The Pipeline Wall provides additional functionality:

• Generating Reports

• Filtering by Date/Time Range

• Filtering by Pipeline Attribute

Generate Reports

To generate a CSV-formatted report of all the Pipelines displayed on the Pipeline Wall, click the Download CSV button.

The CSV file contains the following information:

• Pipeline Link

• Pipeline Name

• Username

• Snaplex

• Status

• Time Started

• Duration

• Document Count

Filter by Date/Time Range

To filter the results by time, you can choose one of the default time ranges:

• 1 Hr: Retrieve Pipelines executed in the past 1 hour.

• 8 Hrs: Retrieve Pipelines executed in the past 8 hours.

• 24 Hrs: Retrieve Pipelines executed in the past 24 hours.

To filter the results by a custom date range, enter dates in the Start and End fields.

Filter by Pipeline Attribute

You can filter Pipelines based on a combination of any of the Pipeline attributes, which you can select using UI controls on the Pipeline Wall.

UI Control	Description
Search box	Filters the results based on the search string you specify. The search string is compared with the following attributes: Pipeline name Username Snaplex/Node name Pipeline parameter values (Learn more: Pipeline Search/Pipeline Filter)
Invocation type	Filters the results based on the method of invocation. You can choose from the following options: All API Calls: Pipelines executed as a Triggered task. Schedule: Pipelines executed as a Scheduled task. Ultra: Pipelines executed as an Ultra task. Manual: Manually executed Pipelines. For Each: Pipelines executed by the For Each Snap. Nested: Pipelines executed by the Pipeline Execute Snap. An icon next to the Pipeline indicates its invocation type. Scheduled Task Triggered Task Ultra Task Manually executed Pipeline Nested Pipeline
Show Only	Filters the results based on the project space. Select a space from the dropdown to return only Pipelines in that space.
Group Pipelines	If selected, displays the parent and child Pipelines in a hierarchical tree. If one Pipeline calls another, a plus sign (+) appears next to the parent Pipeline. You can click on the plus sign to see the child Pipelines that the parent calls. Note Child Pipelines The Dashboard displays data for only up to 500 child Pipelines, even if the parent has more than 500 children.
Status	Filters the results based on the execution status of the Pipeline. The options vary between two sections. In the Executing Pipelines section: All Queued Started Prepared Stopping Failing Suspending Suspended Resuming In the Pipeline Execution History section: All Stopped Failed Completed Note The Status feature might be visible only if Pipelines exist with different stages of execution.