vectordotdev / vectordotdev/vector
Support `journald` as a Kubernetes log source
Open
Nobody has claimed this yet.
domain: sources
needs: approval
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
We should consider supporting fetching logs from journald instead of via the file source for the kubernetes transform. This should be somewhat simple in the sense we don't need to change message parsing but just where the source of events come from.
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 locating the Kubernetes transform and its existing file-source path, then trace how source events reach the unchanged message-parsing logic. The work is done when journald can provide Kubernetes logs through that path without requiring parsing changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, linux, rust
- Domain
- devops, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100