Targets

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

For instance, default terminal log engine configuration includes four targets: file, syslog, syslog2, mem

trace.target@file.type                    = file

trace.target@file.path                    = file:D:\\profile.log

trace.target@file.pattern                  = <{sequenceNumber}:{threadId}:{timestamp}:{level}:{category} - ({code}) {text} {field} {exception}>

trace.target@syslog.type                  = syslog

trace.target@syslog.instance            = syslog

trace.target@syslog.server              =

trace.target@syslog.pattern              = \t({sequenceNumber})\t({threadId})\t{category}\t{timestamp}\t{level}\t({code})\t{text}\t{exception}\t{field}

trace.target@syslog2.type                = syslog

trace.target@syslog2.instance        = syslog

trace.target@syslog2.server            =

trace.target@syslog2.pattern          = \t({sequenceNumber})\t({threadId})\t{category}\t{timestamp}\t{level}\t({code})\t{text}\t{exception}\t{field}

trace.target@mem.type                = memory

trace.target@mem.size                    = 150

trace.target@mem.pattern                = *** ({threadId}) {category}\t{timestamp}\t{level}\t{text}\t{exception}\t{field}

trace.target@websocket.type                = websocket

trace.target@websocket.instance        = websocket

trace.target@websocket.server            =

trace.target@websocket.pattern          = \t({sequenceNumber})\t({threadId})\t{category}\t{timestamp}\t{level}\t({code})\t{text}\t{exception}\t{field}

Syslog server

 Syslog target is by default initialized with TSS server address or domain name.  In case redundancy is configured on TSS, both Syslog ans Sylog2 targets are initialized and turret send logs to both primary and secondary TSS.

Third party syslog server        

 Customer infrastructure might include a third party Syslog server

 If deployment analysis lead to choose this server for IP Trade component logging, turret configuration can be changed defining the following key in the boot settings (advanced settings):

•trace.target@syslog.server

If you want to add a secondary syslog server, you simply have to define the following key in the boot settings (this setting have to be set in the "Advanced settings" tab):

•trace.target@syslog2.server

WebSocket logging

 Customer might need to use websocket protocol for logging. It can be archived simply by setting the server key for the preconfigured websocket target (trace.target@websocket.server).

 The value must be a valid WebSocket URI (i.e.: ws://10.10.50.21:8080). The IP address should be the TSS IP address or any server address that have a logging service installed. The port can be configured through the TSS Logging Service configuration page of the TSS Component Manager (TSS VA only). To use a Secured WebSocket, use the folowing format: wss://tss_server_iptrade_local.

Remarks

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