This page is for administrators who want to configure options related to logging.
Open the 
System Console. In the top right of the console window, click 
Logging. PhixFlow opens the System Logging properties tab.
For information about the properties toolbar, and about the sections Parent Details, Analysis Models, Description and Audit Summary, see Common Properties. We recommend you always add a Description that explains the purpose of the item you are creating.
For a full list of all the PhixFlow property tabs and windows, see Properties, Windows, Menus and Toolbars.
| Field | Description |
|---|---|
Log Frequency | |
Database Reporting Frequency | The frequency with which records are reported e.g. write a message to the log after every 50000 records have been inserted. |
File Reporting Frequency | The frequency with which records are reported from file imports e.g. write a message to the log after every 50000 records have been imported. |
Maximum Debug Messages | Any message written to a log file as a result of any of the options on this page being ticked will be written as a message of type DEBUG. The value entered here is the maximum number of such messages that can be written to the log file. This helps prevent very large log files being produced if several of these options are left turned on by mistake before a large analysis run. |
Debugging On | If you set this parameter to true PhixFlow will write additional debug messages to the system log file. |
Log Service Requests | If you set this parameter to true PhixFlow will write details of Service Requests from the GUI applications into the system log file. |
| Allow Pipe and Data Handler Logging | |
| Allow Logging | If this is set to true logging on pipes and data handlers may be enabled using the System Logging settings below or the Log Traffic settings on individual pipes and data handlers. Changing this setting requires the Enable System Logging privilege. |
Pipe Logging | |
Log Input Multiplier Messages | If you set this parameter to true PhixFlow will write a message to the log every time an Input Multiplier value changes during an analysis run. |
Log Pipe Traffic | If you set this parameter to true PhixFlow will record the number of records returned by all non lookup pipes, in the system log file. |
Log Pipe SQL | If you set this parameter to true PhixFlow will record the details of the queries run by all non lookup pipes on their input streams into the system log file. |
Log Lookup Pipe traffic | If you set this parameter to true PhixFlow will record the number of records returned by lookup pipes, in the system log file. |
Log Lookup Pipe SQL | If you set this parameter to true PhixFlow will record the details of the queries run by lookup pipes on their input streams into the system log file. |
Collector/ Exporter Logging | |
| Log File Collector Traffic | Log the number of records read from files during file imports. |
| Log Database Collector Statements | If you set this parameter to true PhixFlow will write details of the queries run by database collectors (on their target source databases) into the system log file. |
| Log Database Exporter Statements | If you set this parameter to true PhixFlow will write details of the queries run by database exporters (on their target source databases) into the system log file. |
Log HTTP Collector Connection Details | If you set this parameter to true PhixFlow will write details of the HTTP connection (URL, headers, request and response body) into the system log file. |
Log HTTP Exporter Connection Details | If you set this parameter to true PhixFlow will write details of the HTTP connection (URL, headers, request and response body) into the system log file. |
| Maximum HTTP Log Length | Maximum number of characters from the request and response body that will be logged in the debug message. |
Log File Names
Log file names can be up to 250 characters long.