Skip to content

feat: use .jsonl for json logs #79

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
redteampanda-ng merged 1 commit into from
Jan 30, 2026
Merged

feat: use .jsonl for json logs #79

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions output/scan-output.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion scanning/examples.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
^^^^^^^^^^^^^^^^^^^^^^^^
Expand Down