View pipeline details

In the Execution overview table, click a pipeline to open its details panel. The panel includes Snap statistics, logs, and pipeline parameters. During development, Snap statistics also show in Designer when developers validate and run pipelines.

The following sections describe elements from the details panel:

Details header

The details panel header provides information about the pipeline and the task that invoked it:


Pipeline details

From the header:

  • Click Open in Designer to view or edit the pipeline.
  • Hide header fields to make more room for the tabs:
    • Click Hide details to hide the header.
    • Click Expand details to show the header.

The following table describes header fields from left to right and top to bottom:

Attributes Metrics
Icon after the pipeline name Indicates the type of task that executed the pipeline:
Task types
Path The environment name, project space, and project name.
Prepared at Pipelines go through a preparation cycle before they execute.
Execution duration The time the pipeline required to complete, not including preparation time.
Owner Usually the user that created the integration. Ownership can be transferred, for example, when a user is removed from the environment.
Executed at The time pipeline execution started.
Invoker For Triggered Task executions or manual runs of AutoSync data pipelines, this field includes the IP address or user ID of the invoker.
Snaplex/node name The Snaplex node that ran the pipeline.
Completed at The time the pipeline finished.
Parent pipeline path For child pipelines, the path to the parent. The path includes the project space name, project name, and pipeline name.
Task name The task that initiated the pipeline run.
Slot Snaplex nodes are configured with a maximum number of slots, or allocated memory spaces. Each Snap uses a slot to execute. This is the count of the number of slots used by the pipeline.
Resumable Resumable pipelines are a subscription feature. This field indicates whether the feature has been enabled for a pipeline.
The header for a FeedMaster Ultra Task execution, as shown in the screenshot below, has the following fields in addition to those described above:
  • Max-in-flight—The threshold for the number of documents a single node processes. Once the execution reaches the threshold, the Snaplex distributes requests to other nodes. The threshold value is set in Ultra Task configuration options.
  • Close reason—When an Ultra Task transitions to completed status, the close reason can be one of the following:
    • Reference no longer exists or is inaccessible
    • Host Snaplex node restarted
    • The Ultra task has been updated
    • The task is no longer active
    • Closing Ultra pipeline instance to balance instances across the Snaplex
Ultra pipeline details header

Snap Statistics

The Snap Statistics tab provides information about each Snap in the pipeline. As a pipeline executes, the Snap statistics update periodically. You can:

  • Click the refresh button next to the search box to refresh the Snap statistics manually.
  • Click any column except View to sort alphabetically or numerically.
  • Click ERROR or WARN to filter Snaps for those statuses.
Snap Statistics tab

The columns include:

  • Duration—Reports time in milliseconds, fractional seconds, or fractional minutes. For instance, in the Pipeline Execute3 Snap shown above, the .05 fraction of minutes equals .05*60 seconds or 3 seconds. The total execution time for the Snap is 15 minutes and 3 seconds.
  • View—Snap views accept documents to be processed or they output documents. Each view has its own statistics for the number of documents processed and the rate at which the documents flow through the view.
  • Bytes—Only populated for Snaps with Binary views. Values indicate the quantity of data that passed through the view.
  • Documents—The number of structured or binary documents that passed through the view. Binary views can process multiple documents, for example, the ZipFile Reader Snap outputs a binary document for each file in the ZIP archive.
  • Rate—An approximate calculation of how many documents pass through the view per second. For Snaps with binary views, the byte rate is also displayed.

Snap warnings and errors

Warnings display for Snaps when the system detects a potential issue that you can address. For example, pipelines that use a deprecated version of the Join Snap display a warning. Pipeline executions with warnings show up in the execution table with a warning icon. Warnings include:

  • Deprecated Snap: Snaps that are no longer supported should be replaced with newer versions of the Snap to avoid any potential issues.
  • Passing a string to the toLocaleDateTimeString(), toLocaleDateString(), and toLocaleTimeString() methods: Early versions of these methods would only accept a JSON-encoded string for the format argument. More recent versions accept an object literal, which is significantly faster and compliant with the ECMAScript standard.
  • Passing a JSON-Path to the hasOwnProperty() method: The hasOwnProperty() incorrectly treated its argument as a JSON-Path instead of a plain property name.

Pipeline Logs tab

The Pipeline Logs tab shows the logs generated during execution. Monitor only retains execution records for 45 days. Environment admins can find and download logs older than 45 days in Monitor from the Classic Manager Runtime Archive.

Logs contain the following information for the pipeline execution:

  • Process
  • Timestamp
  • Log level
  • Runtime ID
  • File
  • Message
  • Snap Label
  • Exception
Pipeline details logs tab

From this tab you can:

  • Click a button to change the log level.
  • Click the download button to download the logs or a runtime dump in JSON format. With the optional Optional Telemetry subscription, Groundplex users can have logs sent to third-party tools that support OTEL. Refer to Third Party Observability Tools Integration.

Pipeline Parameters tab

The Pipeline Parameters tab shows parameters defined in pipeline settings. Parameters must be configured to capture for the values to show in the execution record. The following example has a parameter, but the Snap properties aren't set to capture the value:

Pipeline details logs tab

State Transition tab

The State Transition tab updates with a precise timestamp as the pipeline transitions from preparing to the completed state: