The Systemite.SystemWeaver.TcpSubServer.exe.nlog is now offering the first version of a configurable option for logging specific user operations and usage statistics. The actions, events and calls currently included in the log are listed below. The events and calls from both the client application and the API will be included, whereas only actions performed in the client application will be logged. They can prove to be useful information for Administrators.

User Activity Statistics

The following operations in the server are included in the log file. 



The printing of a Document or Report. 

For Documents: 

For Reports: 


The export of XML files.

For XML generation: 

For XML Export: 


The export of data to MS Excel (or csv), i.e., export data from a configured grid.


The saving of a Document or Report to an RTF and RVF file save a SysW document or report to RTF

For Documents: 

For Reports: 


The following deletion operations are logged. 


An item is deleted from the server.  


A part is deleted from the server.


An issue is deleted from the server. 

Usage Statistics

The following usage statistics are logged.


A client login to the server.


  • A count of the number of user logins (i.e., active connections)
  • A count of the number of concurrent Read/Write licenses in use
  • A count of the number of concurrent Viewer licenses in use

Reading and Analyzing the Log

The Statistics log is JSON formated and can easily be read, analyzed and visualized using an external tool of choice, such as ELK (Elasticsearch, Logstash, and Kibana) which is open source. One solution is to install, for example, docker and include an image of ELK there.


  • The shipper application used, e.g., beats, should be installed on the same server machine as the SystemWeaver server application and Statistics log file
  • The docker should be installed on a different server than where SystemWeaver server is installed


In the below example, the log file is read by beats. and the data is then parsed and transformed by Logstash. Next, Elasticsearch is used for searching and analyzing. Finally, results can then be presented using Kibana.