Repository navigation
feat: usage telemetry on by default in Community, said loudly - #430
Merged
Merged
Conversation
Community instances send the anonymous daily ping unless told not to; Enterprise stays off unless TELEMETRY_ENABLED=true. DO_NOT_TRACK turns it off whatever else says. When it is on, the API logs it at startup with how to turn it off, and tripl install says so when it writes a new .env (which leaves TELEMETRY_ENABLED commented out; --telemetry / --no-telemetry write it). The dev stack keeps it off. Runtime settings name each reason. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Usage telemetry flips from opt-in to on-by-default for Community. Nobody runs tripl in production yet, so no existing install's consent changes in practice.
Behaviour
TELEMETRY_ENABLEDunset → on in Community, off in Enterprise.falseturns it off;trueturns it on in Enterprise.DO_NOT_TRACK(the cross-tool opt-out) turns it off whateverTELEMETRY_ENABLEDsays. Passed throughcompose.yaml(and the CLI's packaged copy).Anonymous usage telemetry is ON: one small ping a day to … What it holds: https://docs.tripl.io/run/telemetry. Turn it off with TELEMETRY_ENABLED=false (or DO_NOT_TRACK=1) and restart.tripl install:--telemetrybecomes--telemetry / --no-telemetry. Neither leavesTELEMETRY_ENABLEDcommented out in the new.env(the edition's default applies), andinstallthen says on stderr that telemetry is on and how to turn it off. Either flag writestrue/false.compose.dev.yamlsetsTELEMETRY_ENABLED=false: a developer's or CI's stack never pings. A public demo still never sends.DO_NOT_TRACK is set,TELEMETRY_ENABLED=false,Enterprise default.Docs: telemetry (rewritten: on/off, the startup line, retention on the receiver; the engine list now covers all ten), configuration (
TELEMETRY_ENABLEDdefault, newDO_NOT_TRACK), CLI reference, deployment,.env.example.The receiver behind
telemetry.tripl.iois a separate private service; it goes live before this matters.Tests: backend
test_telemetry.py(edition default, DO_NOT_TRACK, the startup line and its absence), CLI install notice per flag/edition and the rendered.env,TelemetryCardreasons, e2e spec updated for the dev stack's explicitfalse. Ran locally: backend telemetry + config/compose tests, the CLI suite, the card's vitest, lint/types;make sync-typesclean.🤖 Generated with Claude Code