fix(telemetry): drop web opt-out toggle, document CLI opt-out in README#65
Merged
lukeocodes merged 1 commit intomainfrom May 8, 2026
Merged
fix(telemetry): drop web opt-out toggle, document CLI opt-out in README#65lukeocodes merged 1 commit intomainfrom
lukeocodes merged 1 commit intomainfrom
Conversation
The web toggle gated only the marketing site's own Sentry init via localStorage — it could never affect the locally-installed CLI's telemetry, since they run in different processes on different machines. Removing it (and the now-dead localStorage check) so Sentry init on cli.deepgram.com is unconditional for visitors. Documenting all three CLI opt-out paths in the main README only: - dg config set telemetry.enabled false (persistent) - DEEPCTL_TELEMETRY_DISABLED=1 (one-shot / CI) - DEEPCTL_TELEMETRY_DSN (fork / self-hosted override) The --help footer keeps pointing at the config command for in-terminal discoverability.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #59. Three small fixes:
cli.deepgram.com. The marketing site's Sentry init is non-opt-outable error/uptime monitoring — same model as every other public Deepgram web property. The toggle implied the visitor had agency over it, which they don't.localStorage.dg_telemetrygate inweb/sentry.client.config.ts. Without the toggle UI it was dead code, but it also let a power user disable site error monitoring via DevTools, which is not the intent. Sentry init is now unconditional for site visitors.dg config set telemetry.enabled false,DEEPCTL_TELEMETRY_DISABLED=1,DEEPCTL_TELEMETRY_DSN) were only discoverable via--helpor source code. Now they live in a## Telemetrysection right after## Configurationwith what's collected, what's scrubbed, and where it lands.Why two telemetry surfaces, one opt-out story
cli.deepgram.comSentrydeepctlSentryThe CLI phones home from the user's machine on user-side stack traces, so opt-out is mandatory and has to be discoverable. The website Sentry catches our own bugs in our own code on our own deployed site. Different consent model, different surface.
Test plan
web/sentry.client.config.ts— Sentry init runs unconditionally; nolocalStoragereadsweb/src/pages/index.astro— footer is just the copyright line; grep fordg-tel/dg_telemetry/Telemetry:returns nothingREADME.md— new## Telemetrysection between## Configurationand## DevelopmentRelated