Audit Trail Control (Debugger): Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
__TOC__ | __TOC__ | ||
The Client captures and displays Model 204 audit trail lines in the audit tab. The audit trail can become very large, and cause the client to consume large amounts or resources on the workstation. | The Client captures and displays Model 204 audit trail lines in the audit tab. The audit trail can become very large, and cause the client to consume large amounts or resources on the workstation. This can be controlled in the ''debuggerConfig.xml'' via the ''<auditLines>'' tag: | ||
<p class="syntax"><debuggerConfig version="1.0> | <p class="syntax"><debuggerConfig version="1.0> | ||
Latest revision as of 15:32, 7 April 2023
The Client captures and displays Model 204 audit trail lines in the audit tab. The audit trail can become very large, and cause the client to consume large amounts or resources on the workstation. This can be controlled in the debuggerConfig.xml via the <auditLines> tag:
<debuggerConfig version="1.0> ... <auditLines> <mode>{none|limited|all}</mode> <maxLines>nnnn</maxLines> </auditLines> ...
mode:
- none - capture no audit
- limited (default) - capture and display no more than maxLines lines of audit trail
- all - capture and display all audit lines
maxLines:
- The maximum number of lines of audit trail for limited mode
- 100 <= maxLines <= 32000
- Defaults to 200