- 20 Sep 2022
- 5 Minutes to read
- Updated on 20 Sep 2022
- 5 Minutes to read
Additionally, Settings.xml should be backed up before making any changes to the Logging Settings.
Through various methods, Administrators are provided options that allow the configuration of various logging parameters such as Log File Size, API Call Timeouts, and Database Timeouts that are recorded in the Decisions Logs.
These settings affect Logs that are recorded in the Logging Tool (System > Administration > System Tools). The following article covers the respective function and configuration of each Logging Setting.
Available Logging Settings
|Logging Setting Name||Default Value||Description|
|5||Prompts for a time threshold (seconds) that if an API call exceeds will then be recorded in the log.|
|LogCheckFieldTypes||False||When set to True, verifies the types of fields used in WHERE clauses. Logs under CheckTypesLogger category at Debug, Warn, and Error if it finds mismatch levels|
|LogDebug/LogInfo||False||When set to True, records event types of this level in the log. Since these levels of event types occur frequently, users may experience performance and/or log size issues as the system continuously records them.|
|True||Records these event types in the log by default as indicated by their True value. Setting this to False stops recording these events in the log.|
It is recommended to keep these as True to aid any future troubleshooting. Errors and Fatal Errors are also logged as Windows Events for monitoring by external tools.
|LogFileMaxSize||10,485,760||Prompts for the max file size (bytes) of a log.|
The default 10,485,760 bytes equates to a maximum limit of about 10.49 MB.
The maximum configurable limit is maxInt32 aka 2,147,483,647 bytes aka 2.14 GB.
|1000||Prompts for a time threshold (milliseconds) that if a Flow step exceeds will then be recorded in the log.|
The default 1,000 value equals one second, so any steps taking longer than this will be in the log.
|LogMaxBackups||10||Prompts for the maximum amount of backups a Log file can create of itself.|
For example, the Decisions Logs folder may contain some log files with the same name but with a number after the name. These numbered logs are backups made before a new log is created.
|LogsDirectory||C:\Users\[Name]\Downloads\Logs||Prompts for the file path Installer Logs will reside. This is usually located at the same place as the Installer. This cannot be changed.|
|5||Prompts for a time threshold (seconds) that if an SQL statement exceeds will then be recorded in the log.|
|CaptureAspNetLogs||False||Enables Kestrel Access Logging and generates Asp.net core Logs (file typically contains "Microsoft.AspNetCore" in the Logs/webserverlogs.|
|CaptureW3CLogs||False||Enables Kestrel Access Logging and generates W3C Logs in Logs/webserverlogs folder. If setting is not present in Settings.xml, the following may be added to enable it:|
|AspNetLogsFileCountLimit||30||The number of files retained for AspNet Log; this is used by both CaptureW3CLogs as well as CaptureAspNetLogs.|
|AspNetLogsFileSizeLimit||104857600||The max size (bytes) of each individual AspNetLog file; this is used by both CaptureW3Logs as well as CaptureAspNetLogs.|
Accessing and Editing Settings
Logging Settings can be accessed through one of the following methods:
- via the Decisions Installer (DecisionsServerInstaller.exe)
- via the Settings.xml file
- via the System Settings in the Decisions Studio
Though many Settings can be accessed throughout each method, some Settings, such as ""LogSQLStatementsTakingMoreThanSeconds", require additional configuration or adjustment via Settings.xml or DecisionsServerInstaller.exe.
- From DecisionsServerInstaller.exe, click EDIT SETTINGS.
- Navigate to Settings containing the word "Log". Adjust the Settings as desired in the column to the right of the Setting's name.
Once Settings have been established as desired, click Save.
- After the Settings have been applied, click RESTART SERVICE.
- From C:\Program Files\Decisions\Decisions Server, open Settings.xml in a text editor (ex: Notepad).
- Change the value(s) between the respective Logging open/close tags.
For example, <LogMaxBackups>10</LogMaxBackups> may be changed to <LogMaxBackups>15</LogMaxBackups>.
- Save and close the text editor.
- Restart Decisions.
- From the Studio, navigate to the Settings Folder.
- Open Logging Settings.
- A list of levels that define how the logs will be stored will be displayed. From the list, right click the logging level and select Edit. In this case, File System was used.
- A dialog box will open covering settings that can be used to define the log settings. Below is a breakdown of each property that can be found for any level. Once the settings have been defined, click OK.
|Use Global Setting||Available for any logging level that is not Global. If enabled, properties defined for the logging level will be overwritten by what is defined under the Global level.|
|Levels||This setting defines what information will be recorded within the logs. The levels are Verbose, Debug, Information, Warning, Error, and Fatal. By default, only Warning, Error, and Fatal are enabled.|
|Log Categories||Selecting Add will open another dialog box, where log categories can be selected. If a category is defined, then only information from the related category will appear.|
|Log Usage Data||Available only at the File System level, this field controls whether heartbeat data will be included in the Decisions.Web.Core logs. This field is enabled by default.|
|Log File Max Size||Available only at the File System level. Defines the max file size for the log file. When the max size is reached for a log file, a new file will be generated.|
|Log File Backup Limit||Available only at the File System level. Defines the max amount of generated log files stored on the file system. When the limit is reached, the oldest log file will be deleted from the File System.|
The LogSettings.json file can be found in the C:\Program Files\Decisions\Decisions Server folder in the File System
This file is used to control the behavior of Logging events at the Local level within the File System. Log Category Settings like Category Name or Level can be adjusted in this file.
After using the Log step, a new Category is automatically created in the LogCategorySettings. The given name for this Category is the name that was previously defined in the Properties tab of the Log step within the Flow.
Enabling Web Server Logs in Self Hosted Environments
- Navigate to C:\\Program Files\Decisions\Decisions Server.
- As an Administrator, Open Settings.XML using a text editor (ex: Notepad).
- Change the <CaptureAspNetLogs>...</CaptureAspNetLogs> value from false to true.
- Save and close Settings.xml.
- Restart Decisions.
Enable Console Logging
In addition to viewing the logs within Decisions, Logs can be recorded and displayed in a console. This feature can be used for instances of Decisions running in containers, allowing logs to be viewed from the console window.
To view logs within a console, the specified logging levels will need to be enabled, along with having Decisions initiated from a console if it is not currently hosted in a container. If Decisions is currently hosted as a container, then the first two steps can be skipped.
- Stop the Decisions Service.
- Launch a command prompt and navigate to the Decisions Server folder. Run Decisions.Web.Core.exe.
- In Decisions, navigate to System > Settings > Logging Settings.
- Left click on Logging Settings, then right click on Console > Edit
- Enable or disable specific log levels. Levels that are enabled will appear in the logs.
Encrypting Session IDs for Logs
For versions 8.5 and above, Session IDs found in log files can be encrypted within a log file. This is done through the ObfuscateSessionIDInLogs property in the Settings.xml. However, this property will need to be manually added for versions upgrading to 8.5+.
- To add the property, run the Decisions Installer.
- Once the Installer has opened, select Edit Settings
- Locate ObfuscateSessionIDInLogs property and set the property to True.
- Save and Restart Decisions.
Once the environment has been restarted, the property will appear in the Settings.xml. Once enabled, any logs which contain a Session ID will be encrypted.