Skip to content

feat(cli): replace HashiCorp telemetry with Sentry analytics#62

Draft
so0k wants to merge 2 commits intomainfrom
002-remove-hashicorp-telemetry
Draft

feat(cli): replace HashiCorp telemetry with Sentry analytics#62
so0k wants to merge 2 commits intomainfrom
002-remove-hashicorp-telemetry

Conversation

@so0k
Copy link
Contributor

@so0k so0k commented Mar 20, 2026

Summary

  • Defines feature specification for #48 — CLI telemetry currently sends data to HashiCorp's checkpoint-api.hashicorp.com
  • Migrates usage analytics (command invocations, language, timing) to Sentry custom metrics instead of simply deleting them
  • Adds independent sendUsageTelemetry config flag alongside existing sendCrashReports, with CHECKPOINT_DISABLE env var preserved as backward-compatible override
  • Three research spikes: checkpoint usage analysis, Sentry migration feasibility, and testing strategy/SDK validation
  • Closes all completed 001-cdktn-package-rename tasks (rename published)

Key decisions

  • Sentry over deletion: Project has full Sentry business plan with OSS support — preserves analytics at no cost
  • No SDK upgrade needed: @sentry/node@7.120.4 already supports Sentry.metrics.increment() etc.
  • Two independent consent flags: sendCrashReports (crashes) + sendUsageTelemetry (analytics) in cdktf.json
  • CHECKPOINT_DISABLE preserved: Overrides usage telemetry, no CI workflow changes needed (14 locations)
  • 7 call sites: Mechanical conversion from HashiCorp POST to Sentry metric emission

Test plan

  • Review spec for completeness and accuracy
  • Review research spikes for correctness
  • Validate consent model (two flags + env var override)
  • Proceed to /specledger.plan for implementation planning

Resolves #48

🤖 Generated with Claude Code

so0k and others added 2 commits March 20, 2026 17:58
Define feature specification and research for GitHub Issue #48.
Migrate usage telemetry from HashiCorp's checkpoint-api to Sentry
custom metrics, with independent consent flags and CHECKPOINT_DISABLE
backward compatibility.

Closes task tracking for 001-cdktn-package-rename (rename complete).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
BREAKING: Major restructuring of project principles.

- Remove "Community Alignment" (process gate in specledger.io, not artifact principle)
- Merge "API Consistency" + "Cross-Language Parity" into "IV. Cross-Language Consistency"
- Add "VIII. Quickstart-Driven Testing" principle
- Renumber remaining principles (VI→V, VII→VI, IX→VII)
- Update amendment procedure to gate through specledger.io spec approval

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@so0k so0k force-pushed the 002-remove-hashicorp-telemetry branch from 2390a28 to 3d67163 Compare March 20, 2026 10:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

cdktn-cli: telemetry uses HashiCorp's endpoint

1 participant