vectordotdev / vectordotdev/vector
New `kubernetes_system_events` source
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
Kubernetes exposes an event stream for system events. I'd like to collect these as an option and run them through the pipeline like any other log event.
Prior Art
- https://github.com/heptiolabs/eventrouter
- https://github.com/kubernetes-retired/heapster
- https://docs.datadoghq.com/agent/kubernetes/event_collection/
- https://docs.newrelic.com/docs/integrations/kubernetes-integration/kubernetes-events/new-relic-kubernetes-events-integration
Helpful info
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 with the Kubernetes event documentation and the linked event-router, Heapster, Datadog, and New Relic prior art to understand the event stream and collection model. Determine how a kubernetes_system_events source should expose system events and pass them through Vector's existing log-event pipeline; done means the source is available as an option and events are collected and processed like other log events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- observability, stream-processing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100