[feature] Telemetry for docker/CLI
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Description
We can't make good decision on docker/cli features without knowing how it get used by real users. For this purpose, Docker Desktop comes with some telemetry support, but obviously we're then missing a significant user base (Linux installations) and usages (CI, production).
I suggest we implement telemetry in docker/cli, as a replacement for https://github.com/docker/compose-cli/tree/main/cli/metrics
Should also support https://consoledonottrack.com/ for users to opt-out.
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 reading the referenced compose-cli cli/metrics tree and locating the corresponding Docker CLI entry points. Clarify the telemetry scope, collection behavior, and consoledonottrack opt-out before implementation; done requires an agreed design for these decisions and validation of the resulting behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100