Add Journal.Fields artifact#1287
Closed
misje wants to merge 2 commits into
Closed
Conversation
Contributor
Author
|
Closing in favour of Velocidex/velociraptor#4933. |
scudette
pushed a commit
to Velocidex/velociraptor
that referenced
this pull request
Jul 24, 2026
This replaces Velocidex/velociraptor-docs#1287. The included journal files do not provide a lot of test data, but at least some.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Starting with the original, now abandoned, native parser of the systemd journal in VQL's binary parser (i.e. the native VQL binary parsing attempt, now moved into go), I saw a need to extract the indexes. Initially I just wanted to list boots. Then, as I dug deeper into the journal format, I decided to make the in-VQL parser more general.
Initial goal: Simply get a list of boots.
Since I realised that
has real forensical value. This artifact provides both, and you specify which (or both) you want.
The collection is very fast and quickly retrieves a lot of unique values for a lot of journal keys, like _SYSTEMD and _COMM/_EXE.
I do not mind at all putting in the extra work needed to get this into the main project. As long as there is enough data in the test journal files.