Icon

JKISeason2-17

Challenge 17: Better Workflows with Error Handling and Logging

Challenge 17: Better Workflows with Error Handling and LoggingLevel: HardDescription: The goal of this challenge is to remind you of the importance of building robust solutions with error handling and logging. These are best practices in workflowdevelopment that are often forgotten, but make a big difference in the end -- especially if the application is critical or if you are working with a team. Concretely, you will pickany workflow of your choice and add the following elements to it: Error handling: Use the Try & Catch construction;Logging - Extract the workflow name, username, start and end of the execution. Next, create a table containing these metadata as well as the name of a failing node (if any)and its message in one row, and write this table to a CSV file. Make sure that once the workflow is executed again, a new row is appended to the log table in the CSV file.Optionally, you can add more columns to your log file, e.g., the column with a custom message depending on the execution status - success or failure. You can also create alogging component that takes workflow name, username, start and end of the execution as input, allows configuring the custom message, and updates the log file. Sales Data.xlsxstandart workflow beginmonth yearyearmonthstandart worklfowendTRYCATCHtop :w/o errorsbottom :errorsbottomNode 34Node 36Node 37Node 38log.csvstart_timeend_time Excel Reader String to Date&Time Extract Date&TimeFields GroupBy GroupBy Visuals Try (Data Ports) Catch Errors(Data Ports) Variable toTable Row Extract ContextProperties IF Switch Merge Variables Table Creator Table Rowto Variable End IF ConstantValue Column ConstantValue Column Column Resorter CSV Writer Create Date&TimeRange Table Rowto Variable Create Date&TimeRange Table Rowto Variable Challenge 17: Better Workflows with Error Handling and LoggingLevel: HardDescription: The goal of this challenge is to remind you of the importance of building robust solutions with error handling and logging. These are best practices in workflowdevelopment that are often forgotten, but make a big difference in the end -- especially if the application is critical or if you are working with a team. Concretely, you will pickany workflow of your choice and add the following elements to it: Error handling: Use the Try & Catch construction;Logging - Extract the workflow name, username, start and end of the execution. Next, create a table containing these metadata as well as the name of a failing node (if any)and its message in one row, and write this table to a CSV file. Make sure that once the workflow is executed again, a new row is appended to the log table in the CSV file.Optionally, you can add more columns to your log file, e.g., the column with a custom message depending on the execution status - success or failure. You can also create alogging component that takes workflow name, username, start and end of the execution as input, allows configuring the custom message, and updates the log file. Sales Data.xlsxstandart workflow beginmonth yearyearmonthstandart worklfowendTRYCATCHtop :w/o errorsbottom :errorsbottomNode 34Node 36Node 37Node 38log.csvstart_timeend_time Excel Reader String to Date&Time Extract Date&TimeFields GroupBy GroupBy Visuals Try (Data Ports) Catch Errors(Data Ports) Variable toTable Row Extract ContextProperties IF Switch Merge Variables Table Creator Table Rowto Variable End IF ConstantValue Column ConstantValue Column Column Resorter CSV Writer Create Date&TimeRange Table Rowto Variable Create Date&TimeRange Table Rowto Variable

Nodes

Extensions

Links

Download

To use this workflow in KNIME, download it from the below URL and open it in KNIME:

Download Workflow
Created by: yilmaer
Created at: 2023-06-01
On NodePit since: 2023-07-21
Last update: 2024-04-26
Created with KNIME version: v4.7.2
Tags: JKISeason2-17

Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.

Try NodePit Runner!