From c248b9a79b195d3d7e1b0f8c9727d8c86af41ae2 Mon Sep 17 00:00:00 2001 From: Max Altgelt Date: Fri, 30 Jan 2026 11:52:15 +0100 Subject: [PATCH] feat: use .jsonl for json logs --- output/scan-output.rst | 4 ++-- scanning/examples.rst | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/output/scan-output.rst b/output/scan-output.rst index 4069de5..eec8183 100644 --- a/output/scan-output.rst +++ b/output/scan-output.rst @@ -19,8 +19,8 @@ THOR creates several files during and at the end of the scan. You can define different formatting options for both text log and SYSLOG output. -JSON File Output (.json) -^^^^^^^^^^^^^^^^^^^^^^^^ +JSON File Output (.jsonl) +^^^^^^^^^^^^^^^^^^^^^^^^^ The JSON log file is written by default. It provides the scan results in a structured, machine readable format. See https://github.com/NextronSystems/jsonlog diff --git a/scanning/examples.rst b/scanning/examples.rst index 55c0979..7323634 100644 --- a/scanning/examples.rst +++ b/scanning/examples.rst @@ -15,7 +15,7 @@ access rights on the share. .. code-block:: doscon - C:\thor>thor64.exe --no-html --no-csv --json \\sys\rep\%COMPUTERNAME%_thor.json + C:\thor>thor64.exe --no-html --no-csv --json \\sys\rep\%COMPUTERNAME%_thor.jsonl Logging to Syslog Server ^^^^^^^^^^^^^^^^^^^^^^^^