Remote journald services for systemd log collection. #596
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.
Description of changes
This draft PR is only intended to share my config to upload and receive systemd journals remotely for debug purposes.
Changes:
withRemote
in base systemd configsystemd-journal-upload
service, exposed with the optionwithRemoteJournal
. It allows to set the target IP, by default it is set to thenetvm
heresystemd-journal-remote
service, exposed viawithRemoteJournalServer
netvm
. You can retrieve all logs from thenetvm
in this configuration, e.g., viascp
Note: This is an insecure configuration and should only be used for debug purposes, as it uses
http
and adds a route from host.Checklist for things done
x86_64
aarch64
riscv64
nix flake check --accept-flake-config
and it passesTesting