Event logging

​All calls to the archive are logged internally, with a userId and a tracking code. The userId is intended to contain an id of the end user initiating the operation. If no end user is directly involved, a system identifier (for instance a system name) should be used instead.


The tracking code is an identifier intended to show that multiple backend operations are part of the same end user action. This is used both internally in the archive (where a REST call for instance may cause a number of internal operations that are logged separately), or for client implementations where one operation in the client system at a customer causes multiple REST calls to be made. The tracking code does not need to be unique. However, since it is used to separate what calls belong together in the log, the same value should not be used twice within a short time period. It is for instance not a good idea to use timestamps, since if two calls happens at the same time, they will also get the same timestamp, and it will seem like one operation. A good value would be a simple rotating sequence number.

The userId can be up to 50 characters, while the tracking code can be up to 30 characters.


These logs are only accessible by administrators in Nets. Individual log entries can be manually extracted and sent to a customer administrator on request. While Nets on a general basis is licensed to handle personal information, it is the customers responsibility to chose a userId that can be stored over time. The most common examples are the use of social security/personal numbers or email addresses.