...
Standard procedure for a project is to set log level to Verbose during the project and the first 3-6 months after the project. Log level shall then be changed to Error, to avoid log files to grow too quickly. Log file location shall be a non application/system disk.
Manager
Manager writes logs for a specific user to AssertManager.log. Log file is accessible through the Help menu in the Manager application. Logging is controlled by settings.config for the user.
File name: settings.config
Location: %AppData%\Signifikant\Assert
Code Block | ||
---|---|---|
| ||
<LogLevel>Verbose</LogLevel>
<LogDebugWrites>true</LogDebugWrites> |
Server
Server will write log entries to AssertServer.log. Log level can be set to Critical, Error, Warning, Information and Verbose. Log files generated by Server are controlled by server.config located in ProgramData.
File name: server server.config
Location: C:\ProgramData\Signifikant\Assert\
Code Block | ||
---|---|---|
| ||
<?xml version="1.0"?>
<ServerConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<LogLevel>Verbose</LogLevel>
<LogFilePath>c:\log\AssertServer.log</LogFilePath>
<!-- Starting version 5.1.5 it is possible to get extended logging by turning on debug writes. -->
<LogDebugWrites>true</LogDebugWrites>
</ServerConfiguration> |
Web Viewer
...
If several triggers exist, extended logging will be triggered if all triggers are valid.
Tag | Usage | Sample | ||||
---|---|---|---|---|---|---|
level | The log level. Default is Verbose which matches all log messages. Valid values are Verbose, Information, Warning, Error, Critical |
will trigger extended logging for all log entries of level Error and above. | ||||
url | Url accessed. The url is expressed as a regex. |
will match
| ||||
message | A regex pattern to match against the original message part of the log message. |
will match
| ||||
method | A regex pattern to match against the calling method. |
will match
| ||||
exception | A regex pattern to match against the exception message and stack trace | |||||
url-referrer | A regex pattern to match against the url referrer of the request. The url referrer is url of the origin of the request. |
If several triggers exist, extended logging will be triggered if all triggers are valid. E.g.
...
Each tag is true/false. By default all tags are set to true.
Tag | Usage |
---|---|
stack-trace | true to print stack trace. |
request | true to print information such as url, url referrer, cookies, headers, user agent of the request. |
cookie | true to print the http cookies for the request. |
site | true to print site information. |
state | true to print state information. |
user | true to print user information. Also print the proxy user. |
permissions | true to print the combined permissions (user, server and dynamic permissions) for the request. |
configuration | true to print unique id of configuration. |
culture | true to print culture information (calculated display, data and document cultures and fallbacks). |
presentation-context | true to print the presentation context. |
custom-context | true to print custom context information. |
thread | true to print current thread information. |
Related articles
Filter by label (Content by label) | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Page Properties | ||
---|---|---|
| ||
|