Adding a diagnostic log component to an automation

Follow these steps to add a diagnostic log component to an automation.

1. Ensure the necessary automation is open in a Designer window.
2. Determine the existing automation design blocks between which to place the log component.
3. Delete the automation link connecting the two automation design blocks.
4. From the Toolbox window, locate and expand the Advanced category.
   
5. Drag and drop the DiagnosticsLog component to the automation. A diagnosticsLog1 is displayed in the automation and on the Local variable tab.
   
6. Rename the diagnosticLog1 component based on project documentation.
   Note: To name a diagnosticLog component, follow the Log_{name of the automation} naming convention.
   
7. On the diagnosticsLog1 Design block, click message to enter the custom log file entry. You can also pass a dynamic value through the input port.
8. Connect the diagnosticLog1 Design block with the automation links to the automation.
9. In the Object Hierarchy, click the diagnosticLog1 object. The Properties window updates to display the log component.
10. In the Properties window, modify the Mode and Type properties as needed.
    
11. From the menu bar, click File > Save All to save your changes.

Follow these steps to validate the recorded log entry.

1. Navigate to the directory where the log file exists.
   Note: The default location can be identified by entering %appdata% in the address bar of File Explorer.
2. Double-click the RuntimeLog.txt file to open the log file. The file can be opened in Notepad or another application.
3. View the log data. the following image is an sample log file.
   
4. Close the log file application.