Skip to content

feat(ENG-15367): add cloudsmith telemetry status, id and reset - #572

Draft
tigh-latte wants to merge 1 commit into
eng-14331-4-capturefrom
eng-14331-5-command
Draft

tigh-latte wants to merge 1 commit into
eng-14331-4-capturefrom
eng-14331-5-command

Conversation

@tigh-latte

@tigh-latte tigh-latte commented Oct 29, 2026 •

Copy link
Copy Markdown
Collaborator

Usage telemetry stack, part 5 of 6. Builds on #571. Next: #573.

Description

This PR adds a cloudsmith telemetry command group, so users can see what usage telemetry is doing and reset their install ID. It also keeps our own CI runs out of the data, and adds the rules for working on telemetry to AGENTS.md.

$ cloudsmith telemetry status
Usage telemetry: off (DO_NOT_TRACK)
Log mode: off
Install ID: on

$ cloudsmith telemetry id
c2537300-c8d7-42bf-b6be-d14e74c2c71f

$ cloudsmith telemetry reset
Install ID deleted. A new one is created on the next command.

status gives the first reason telemetry is off, if it is: an opt-out, a development build, a non-Cloudsmith host and so on. It applies typed flags such as -S the same way the send checks do. The telemetry commands never send telemetry themselves.

Behaviour changes

  • The binaries, dev-release, image-build and release workflows set CLOUDSMITH_NO_TELEMETRY=1 for the steps that run the CLI. Smoke tests are development noise. Because this variable also turns off error reporting, those steps no longer send Sentry reports either. The macOS clean-room smoke test passes it explicitly, since env -i drops the workflow's value.

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation update
  • Refactoring
  • Other (please describe)

Additional Notes

N/A: the CHANGELOG entry and user docs are left out until the design is final.

🤖 Generated with Claude Code

- telemetry status: shows whether usage telemetry would send and why not.
- telemetry id: shows the install ID.
- telemetry reset: deletes the install ID.

Our release, binary and image workflows set CLOUDSMITH_NO_TELEMETRY so
smoke tests send nothing. AGENTS.md gets the rules for working on usage
telemetry.

telemetry status applies typed flags (-S) the same way the send rules
do. The macOS clean-room smoke test passes CLOUDSMITH_NO_TELEMETRY
explicitly, since env -i drops the workflow's value.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tigh-latte tigh-latte changed the title feat(ENG-14331): add cloudsmith telemetry status, id and reset feat(ENG-15367): add cloudsmith telemetry status, id and reset Oct 29, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants