Introduction

Learn about the different logs available in FlowWright Application.

Last published at: September 19th, 2025

As a FlowWright admin, navigate to the Status - Log page. 

 

The System Log UI is rendered below. Please note that the log entries are displayed according to the selected option in the drop-down menu. The log entries are marked by icons representing Low, Medium, High priority, Error, Warning, and Info items. You may use the Search text bar to filter the results. 

 

Select the System Log menu to access the following logs: Audit Log, Data Access Log, Engine Log, Security Log, ETL Log, Microservice Call Log, REST API Log, and Telemetry Configuration.  

 

The FlowWright application writes to various logs while in operation. This includes an Audit Log, Data Access Log, Engine Log, Security Log, ETL Log, Microservices Call Log, REST API log, and Telemetry Configuration, all of which are enabled by default. You cannot deactivate any of the log features.

  • The Audit log records all configuration activities to track who did what and when. This log can be reviewed by occurrence date or source.  
  • The Data Access Log records all events related to client applications and user access to a computer resource. It can be exported as an XML file for further analysis and review.
  • The Engine Log records all events related to errors, starts, stops, maintenance, and internal operations of core services, viz. Process, Archival, Data Bridge, Trigger, Statistics, and Email. This log can be configured to review information by occurrence date or source.
  • The System Log manages errors and information messages logged by the application.  It can be configured to review information by occurrence date or source.  
  • The Security Log records all events when external resources access FlowWright services.  It can be configured to review information by occurrence date or source. 
  • The ETL Log records contain details about the data pipeline's execution, such as data extraction records, transformation activities, data loading status, errors encountered, and processing times. It can be configured to review information by occurrence date or source. 
  • The Microservices Call Log contains detailed event information from individual services, including a unique Correlation ID to link calls across services, timestamps, the service name, the method or function being called, the request payload, and the user triggering the action. 
  • The REST API log is a comprehensive record generated by a REST API that documents all the requests sent to and responses received from the API. It includes information such as the endpoint accessed, the request method, timestamps, response, IP, and the status codes of reactions.
  • The Telemetry Configuration Log shows the mapping between the application log and the DLLs.