A newer version of this documentation is available.

Service Trace

[Service Trace]
:FlushTimeout=333
:MaxSize=10
SeparateProcess=0x07
UpdateTime=0
UseCache=10000

FlushTimeout

The trace server can write the trace to the hard drive immediately, but this can be slow. Setting the FlushTimeout parameter creates a separate thread that records the trace with the flush timeout value interval. Default active with 333 milliseconds.

[Service Trace]
FlushTimeout=333

MaxSize

The MaxSize parameter tells the maximum size in megabytes (MB) of the trace file. The default size is 100 MB.

[Service Trace]
MaxSize=100

SeparateProcess

The property SeparateProcess is used to run the Trace component of Net iD Service as a separate process.

When monitoring is activated it reports status and trace component to %TEMP%/netid_trace_monitor.txt.

#0x01 (1)
#0x02 (2)
#0x04 (3)

[Service Trace]
SeparateProcess=0x07

1	Activate separate process.
2	Activate monitoring of separate process.
3	Activate report of monitoring.

UpdateTime

All trace entries are received with a timestamp, the initial part of each trace entry. This timestamp can be updated when received to be based on the server situation instead.

[Service Trace]
UpdateTime=1 (1)

1	Parameter UpdateTime tells if the value should be updated or not.

Values

0: off
1: on

UseCache

This UseCache parameter is almost the same parameter as Trace > UseCache and replaces the Trace UseCache value if it is active. This value has no effect if FlushTimeout is used.

Specifies the maximum number of trace rows that are allowed to cache.

The trace is quite extensive, so recording the trace can have unwanted effects on performance. The UseCache parameter allows the usage of a write cache in the process. This improves the trace write performance but can complicate the trace analysis.

[Trace]
UseCache=10000

To investigate a crash, you must disable UseCache since no trace is recorded if the application crashes.