Snaplex and node issues

The Node diagnostics table shows the maximum, minimum, recommended, and current values for configurable node parameters to help you maximize performance and avoid issues. It also shows average and peak RAM usage.

To view the Node diagnostics table in Monitor:

  1. Navigate to the System overview page.
  2. Click a node to open the details panel.
  3. Click the Additional details tab.

Pipeline issues

You can run validate and run pipelines in Designer to troubleshoot issues during development. To see more runtime information in Monitor:

  1. With the pipeline open in Designer, in the toolbar, click Execute Pipeline.
  2. In the toolbar, click Pipeline Statistics. The Pipeline Execution Statistics dialog opens.
  3. Click the title to open the record of the pipeline run in the Execution overview as shown below:
    Open Monitor from pipeline statistics in Designer.

To troubleshoot production pipelines that were created in the Designer, the first step is to identify which pipeline encountered an issue. Then, you can:
  • Find the Snap error messages for debugging.
  • Download logs

Find the problem production pipeline

Finding the pipeline to debug can be challenging, especially in environments with tens of thousands of pipelines in production. The error report might come from an external source such as Zendesk. External incident reports often refer to the data by some unique identifier, such as a purchase order number. Because SnapLogic does not store record data or metadata, a simple search in the Execution overview cannot identify the pipeline that processed those records.

Encourage pipeline developers to use the best practices that enable others to find pipelines:

  • Name pipelines using a convention that helps others understand their purpose.
  • Organize related pipelines in logically-named projects in the same Project space. The Execution overview search provides Project Space and project search under advanced options:
    Project space search

  • Document the pipeline purpose and the systems it interacts with. This might be in a document such as a spreadsheet.
  • Use pipeline parameters to capture a value that maps to a record. The Execution overview string search returns results for parameter values.
  • Use error pipelines to output and store record data when a failure occurs.

Identify the Snap error

After locating the problem pipeline in the Execution overview, identify which Snap or Snaps encountered an issue. Click the pipeline to open the details pane. From the details pane, try the following to learn more about the error:

  • Use the Error filter on the Snap statistics and Pipeline logs tabs to bring errors to the top:
    Errors filter

  • Use the All filter on the Pipeline logs tab to find out what happened just before the error.

In the case of errors caused by the data itself, such as formatting issues, you will need to find the issue and fix it in the source. This is easier for pipelines with an error pipeline that stores record data when a failure occurs.

Download logs

To download pipeline logs:

  1. In the Execution overview, click the pipeline execution of interest to open the details panel:

  2. Select the Pipeline Logs tab.
  3. Click download.

    The log downloads to your computer.