Logging SettingsLast Updated: 03/28/2018 Introduced in Version: 2.0
By default, fatal, error-level errors, and warning (non-fatal) errors are captured in the log files, indicated by the True value. Additionally, API calls and Database calls that take longer than 3 seconds are written onto the log. To adjust logging settings, update the settings found in the settings.xml file. View the logs in the Primary.log files.
These instructions assume that the platform is installed in its default location C:\Program Files\Decisions.
Use your installation location when following these steps.
Fatal and error-level errors are also logged as Windows events for monitoring by external tools.
If editing the Settings.xml file, locate the two lines:
Then, change the value to the respective time interval. For example, to capture all SQL statements and/or API calls taking longer than 1 second, replace “3” with “1”.
To log informational errors and errors encountered in the flow Debugger, change the logging level by locating these lines. . .
. . . and changing the value from “false” to “true” for each. Enabling debugger logging makes it possible to see which steps take the longest time, but be warned: logging at these levels will dramatically increase the size of log files over time, and negatively impact performance. These levels should only be turned on when necessary for troubleshooting, or for demonstrations.
Once we restart the Service Host Manager, these changes will take effect and logs will be generated automatically.
Open Services, select Service Host Manager, and restart the service.
Example API log:
Example database log:
Need more help with: