Log files are system administrators’ best friends. Well, they are if they are understandable and useful. The problem with most log files, including most of the so-called “human-readable” ones, are very badly structured, and ultimately only truly understandable by a machine.
For that reason, in the past few years JSON-structured log files have become all the rage. Because they are easily understandable by a human being, and extremely fast to parse for a computerized log analyzer.
So, yes, in Syncplify Server! v6 you will find JSON-structured logs that look pretty much like this:
{ "time":"2021-06-18 13:31:46.781", "level":"info", "nodeId":"peaceful-booth", "sender":"ssh2_sftp-handler", "sessionId":"bCrx5QKuNao73CB9UQTURU", "clientIp":"127.0.0.1", "serverIp":"127.0.0.1", "serverPort":22, "protocol":"ssh2_sftp", "username":"test", "method":"SESSION-START", "uriStem":"", "uriQuery":"", "status":200, "cliToSrvBytes":0, "srvToCliBytes":0, "userAgent":"SSH-2.0-FileZilla_3.52.2" }{ "time":"2021-06-18 13:31:46.786", "level":"info", "nodeId":"peaceful-booth", "sender":"ssh2_sftp-handler", "sessionId":"bCrx5QKuNao73CB9UQTURU", "clientIp":"127.0.0.1", "serverIp":"127.0.0.1", "serverPort":22, "protocol":"ssh2_sftp", "username":"test", "method":"LIST", "uriStem":"/", "uriQuery":"", "status":200, "cliToSrvBytes":0, "srvToCliBytes":0, "userAgent":"SSH-2.0-FileZilla_3.52.2" }{ "time":"2021-06-18 13:31:48.257", "level":"info", "nodeId":"peaceful-booth", "sender":"ssh2_sftp-handler", "sessionId":"bCrx5QKuNao73CB9UQTURU", "clientIp":"127.0.0.1", "serverIp":"127.0.0.1", "serverPort":22, "protocol":"ssh2_sftp", "username":"test", "method":"SESSION-END", "uriStem":"", "uriQuery":"", "status":200, "cliToSrvBytes":0, "srvToCliBytes":0, "userAgent":"SSH-2.0-FileZilla_3.52.2" }
In addition to that, while older versions of our software only supported logging to file or syslog, the next major version will support 4 log targets: file, syslog, database, or stdout.