sdjournal: please add support for journal namespaces
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.7k
- Forks
- 338
- PR merge metrics
- No merged PRs in 30d
Description
I am using sdjournal indirectly with the filebeat journald input, and was wondering if reading from a non-default journald namespace is supported directly. I know that I can point filebeat to the namespace's systemd.journal file residing in /var/lib/journal/machine-id.namespace, but this requires knowledge of the machine-id for each individual server.
I solved the problem for our system by symlinking the machine-id.namespace directory to a machine-independent path, but this still feels hacked together.
Looking at the code it doesn't seem like, so I just wanted to confirm.
Thanks a lot and all the best!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining sdjournal's existing journal-opening and reading APIs, then compare them with systemd journald namespace behavior and the machine-independent path requested. Done means callers can select a non-default namespace without knowing each server's machine-id, with coverage for the namespace case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100