...
If the pipeline fails, you see inline, which Snap failed.
...
If If a Snap writes to its error view, the row in the table will be highlighted in red:
...
The The Automated Pipeline Killer prevents high memory-consuming pipelines from causing node crashes. It tracks pipeline use and reservation of heap and non-heap memory. When the committed and used memory is excessive, it prevents the exhaustion of available memory. The Automated Pipeline Killer identifies the faulty Snap responsible for the high memory utilization, kills that pipeline, and adds an error message to the Snap. The Automated Pipeline Killer:
...
pipeline completed with errors—indicates that a pipeline with error pipeline that processed at least one document.
The error pipeline displays a Completed status. When you hover over the status of the main pipeline, pipeline has snaps that processed error documents is displayed.
pipeline completed with warnings—indicates that warnings occurred for Snaps in the pipeline.
The current set of warnings are as follows:
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.
...
The Duration bar charts provide an overview of how long the pipeline takes during the processing of each document. The width of the chart represents the overall run time of the Snap and is broken down into three sections with different colors:
Input wait time as green.
Execution time as blue.
Output wait time as purple.
The input time and output time are how long the Snap takes waiting for its neighbor Snaps to do their processing. The execution time is how long the Snap takes to process documents. You can mouse over the Duration bar to see the exact amount of time that the Snap takes waiting or executing.
When optimizing a pipeline, you can use the duration bar chart to identify the bottlenecks by looking for Snaps with a large blue bar.
Ultra pipelines have an additional Idle metric that indicates how long the pipeline has been idle and not processing any documents. The idle time is subtracted from the input wait time to indicate where bottlenecks are located in an Ultra pipeline.
The CPU %, Memory, and Net columns display the average resource usage for that Snap.
The CPU usage indicates how much CPU time the Snap itself consumed while working.
The Memory column indicates how much memory is being allocated by the Snap.
The Net column shows how much data the Snap received or transmitted over the network.
If you are seeing high resource usage on your Snaplex node, you can use these metrics to help identify the potential causes. Hovering over these columns will open a dropdown list that shows additional detail.
Each Snap has Views that accept or produce documents to be processed. Each view has its own statistics display for the number of documents processed and the rate at which the documents flow through the view.
The Bytes column populated for Snaps that have binary views and displays the total amount of data that has passed through the view.
The Documents column shows how many structured or binary documents flowed through the view.
Binary Views
Binary views can send multiple documents, for example, a ZipFile Reader Snap will output a separate binary document for each file in the Zip.
The Rate column is a rough approximation of how quickly the documents flow through the view. If the Snap has binary views, the byte rate is also displayed.
When you mouse over the resource columns in a row, the row highlights and a dropdown will appear to show even more information. The top half of the dropdown has sections which display the average usage of a resource for every document that is processed, a chart showing the last minute of activity, and the total usage of the resource over the full run-time of the Snap. The bottom line shows the version and build information for the Snap class.
...
| Note |
|---|
|
The CPU Time displays how much the CPU is consumed.
The Wait Time displays how much time the Snap took waiting for input/output or internal processes.
The Memory Allocated displays the number of bytes that are allocated by the Snap.
| Note |
|---|
|
...
| Info |
|---|
|
...
Pipeline Parameters
While this tab appears for all pipelines, it only displays information for those pipelines that are run either by a task or by another Snap (such as the pipeline Execute Snap). Values are returned only for those parameters that have Capture selected in the pipeline Properties dialog.
...
Path to the pipeline.
The Snaplex node is used to run the pipeline.
The username of the person who ran the pipeline.
The Slot Count. See Maximum Slots on the Node Properties tab on the Update Snaplex dialog.
Resumable Mode displays as Enabled if the pipeline is resumable. If not, the status is Disabled.
The Task name: The name of the Task (if applicable).
The Max-In-Flight value. The maximum number of documents that can be processed by an Ultra task instance at any one time.
The Close reason for when an Ultra task goes into the Completed state.
The Stop Reason occurs when the system is unable to stop the pipeline on the node because the runtime cannot be found. The runtime status is set to Stopped, but the execution duration displayed may not be accurate. The possible execution duration is displayed in milliseconds.
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 Requests. These statistics are displayed during the processing of documents.
Receive Time. The time that the request is received.
Client IP. The IP address that the FeedMaster sees when the load balancer forwards a request.
Original IP. The IP address of the external client that the load balancer, when configured to do so, forwards to the FeedMaster.
Method. The underlying HTTP method of the request.
Size. The size of the document payload in bytes.
Extra Path. The path of the Ultra pipeline task.
The Request History for Ultra tasks. These statistics display the last 100 documents processed in the Ultra pipeline.
Pipeline Monitoring API Available
You can also collect the Ultra history statistics using the pipeline Monitoring API.
Some statistics in common with those from the Ultra Request report are identical.
Receive Time. The time that the request is received.
Processing Time. The total time for the Ultra pipeline to process the documents associated with this request. For example, if the input document is copied, this time includes all the time needed to process each copy.
Client IP. The IP address that the FeedMaster sees when the load balancer forwards a request.
Original IP. The IP address of the external client that the load balancer, when configured to do so, forwards to the FeedMaster.
Method. The underlying HTTP method of the request.
Size. The size of the document payload in bytes.
Response Size. The size of the document in bytes payload inside the response.
Extra Path. The path of the Ultra pipeline task.
State Transition. These statistics display when multiple runs of an Ultra pipeline occur.
State. Current The current state of the Ultra pipeline.
Timestamp. The time that the most recent Ultra pipeline execution occurred.
Username. The username of the person invoking the Ultra pipeline.
...