I was looking for a way to get some (security) audit logging for actions done around Royal Server and got some good hints from Michael on this part :)
There is one point that may be interesting on the RoyalTS/X side and we think that it would be a good idea to create this feature request to see what other users' can contribute as ideas too !
Currently, Royal Server already logs interactions from a RoyalTS/X client allowing us to get details of actions like documents opening and established connections, and also interaction with the configuration tool, but from the Royal Server point of view only.
It would be interesting to add the ability to get tracks of some actions done on objects in a Royal Server's hosted document, this time from the client point of view.
I know that RoyalTS already offer logging capabilities (I definitely need to read the Serilog documentation on how to implement Elasticsearch/Splunk/Syslog forwarding...), but sending this directly to the related Royal Server to limit logs tampering and get a centralized source of knowledge around Royal Server stuff would be great.
For example, these types of actions can be targeted: