Completed executions

Track and monitor deployed integration pipelines' metrics.

A completed execution is the record of what happened inside of the pipeline, from the moment the input passed through the trigger until it ran through the last connector in the pipeline.

In the Completed executions tab, you can keep track of pipeline executions and their log histories. You can also re-execute the pipelines.

Environment selection

You can select the desired environment on the upper left corner of the page. When you select an environment, the whole page refreshes to show the data related to the pipelines in that environment. Each environment is color coded to make identification easier.

Search fields

You can filter pipeline executions using the parameters below. The completed executions are shown below according to the specified parameters.

You can also search for the pipeline executions using the Ctrl+Enter (Windows) or Cmd+Enter (macOS) shortcut as an alternative to the Search button.

• Time Period: You can filter pipelines executed in the last 5, 15, or 60 minutes, or select a specific time interval.

• Message type: The execution status of the pipeline:

  • Response: Executions completed without any interruption.

  • Error: Interrupted executions.

  • All: Any execution.

• Pipeline name: The name of the pipeline.

• Pipeline version: Whether the version of the pipeline is major or minor.

• Pipeline execution key: Identifier of each execution of a pipeline.

• Payload: The pipeline input or output in JSON format. This search field uses Elasticsearch’s simple query string syntax.
• Source: The pipeline trigger.
• Error code: A pipeline execution error code, according to the HTTP Status Code pattern.

Execution details

Click the magnifying glass icon in the row of the execution in the Completed executions table to see the Execution details sidesheet. You can also analyze the pipeline execution within the Canvas by clicking the Open pipeline in a new tab button in the top right corner of the sidesheet.

The Execution details include:

• Pipeline execution key: Identifier of the pipeline execution.

• Request message: The JSON data sent by the pipeline trigger.

• Response message: The pipeline’s JSON output.

Execution logs: The pipeline logs generated by the execution. Click the eye icon to visualize the log message. On this screen, you can copy the message or format the JSON.

• Execution messages: The message is the data that is transmitted through the pipeline. Each component of the pipeline (connectors, triggers, globals, and so on) receives, manipulates, and exports a message. Only the first 50 pipeline messages are shown, and only for pipelines executed in the Execution panel.

In some cases, the Digibee Integration Platform presents truncated payloads, according to the following criteria:

Payload size	Exhibition
Smaller than 32kb	Full exhibition
Between 32kb and 320kb	Partial exhibition
Larger than 320kb	@@DGB_TRUNCATED@@ warning is shown