vectordotdev / vectordotdev/vector
Collect docker events
Open
Nobody has claimed this yet.
have: nice
needs: approval
needs: requirements
platform: docker
source: new
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
Docker offers a docker events command that exposes Docker system events. And here is some prior art.
I'm unsure if these events are represented in the logs, but I wanted to open an issue to represent the discussion. This is somewhat similar to #1293 and #1545. I have similar questions:
- Should we collect these events separately?
- If so, should we define a new
docker_eventssource or add it to the existingdockersource?
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 linked Docker events documentation and the devents prior art, then compare the related discussions in #1293 and #1545. Resolve whether events are already represented in logs and whether they belong in a new docker_events source or the existing docker source; the issue is done when that scope and design are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100