Targets

A trace target is defined by a type and a trace pattern.

For instance, default TSS applications log engine configuration includes three targets: file, eventviewer and db

trace.target@file.path = F:\Syslog

trace.target@file.pattern = {timestamp}\t{level}\t{ipAddress}\t{category}\t{text}\t{fields}\n{exception}

trace.target@file.type = file

trace.target@db.type=db

trace.target@db.pattern={timestamp}\t{level}\t{ipAddress}\t{category}\t{text}\t{fields}\n{exception}

trace.target@eventviewer.log=Application

trace.target@eventviewer.type=eventviewer

trace.target@eventviewer.pattern=--- Text : ---\n{text} \n\n--- Exception : ---\n{exception} \n\n--- Field : ---\n{fields}

trace.target@eventviewer.source=IptradeNet.Console

trace.target@eventviewer.info=info

trace.target@eventviewer.error=error, fatal

trace.target@eventviewer.warning=warn

Remarks

•Creating a new target requires to add it in trace.global.targets value

•By default, no loggers are configured to use the db (database) target. If the database target is configured with a logger, we recommend to not set this logger with the log level debug1 or debug2 as it may overload the database.

•By default, Event Viewer will not log traces with level debug1 and debug2. If the administrator wants to configure it, he should edit the setting key "trace.target@eventviewer.info" to add debug1 and debug2 (trace.target@eventviewer.info=info, debug1, debug2)