Trace
[Trace]
Call=0
MaxSize=100
Path=none|{TS}||server,%WinDir%\\Temp\\netid.txt|{LOGONUI}||server|*
UseCache=10000
UseLocalTime=1Call
Use call trace instead of full trace. Call trace only traces every function call with result code.
Dump, DumpMax
It is possible to use the plugin to store data to a local file. This functionality is used to dump SOAP trace to a file.
SetProperty("Location", "Trace;Dump");
SetProperty("User", name);
SetProperty("Data", _BASE64.encode(_ToArrayOfUTF8(content)));
Invoke("SetLocationData");
[Trace]
Dump=file:///C:\Temp\soap\{name}.xmlThe maximum number of file entries are stored in the same location, and read from plugin:
GetProperty("ConfigGlobal:Trace:DumpMax);
[Trace]
DumpMax=100Path
The trace path sets the location of the trace. The path can specify "server" to send the trace to the trace service. One can also specify an alternative path when used with trace service, and the service is not responding.
[Trace]
Path=C:\Temp\netid.txt
Path=server
Path=server,C:\Temp\netid.txtThe trace path can use environment variables.
[Trace]
Path=%TEMP%\netid.txtUsually the trace service location is specified at Service Trace > Connect, but it is possible to set an alternative path:
[Trace]
Path=server net 192.168.1.100UseCache
The trace is quite extensive, so writing the trace can have an effect on performance. The UseCache parameter allows the use of a write cache in the process. This improves the trace write performance, but can complicate the trace analysis. Specify the maximum number of trace rows that are allowed be to cached.
[Trace]
UseCache=10000| You must disable UseCache when investigating a crash, since the trace will not be written if the application crashes. |