telemetry
Use telemetry commands to inspect and change anonymous CLI telemetry. Telemetry is on by default.
bunx prisma telemetry statuspnpm prisma telemetry statusyarn prisma telemetry statusnpx prisma telemetry status| Command | Description |
|---|---|
telemetry status |
Show whether anonymous CLI telemetry is enabled and why |
telemetry enable |
Enable anonymous CLI telemetry |
telemetry disable |
Disable anonymous CLI telemetry |
telemetry enable and telemetry disable write config.json in the CLI's config directory: $XDG_CONFIG_HOME/prisma/ if that variable is set, otherwise ~/.config/prisma/ on macOS and Linux and %APPDATA%\prisma\ on Windows. The same file holds the random installation id that the first enabled telemetry run creates, right after it prints the notice. telemetry status prints the path it is using. The ORM commands mounted in the unified CLI share this preference; there is no second store to change.
PRISMA_DISABLE_TELEMETRY=1 and DO_NOT_TRACK=1 turn telemetry off for the current CLI invocation. If you set them in a shell profile or CI configuration, they apply to every prisma run in that environment. The full list, and what to rename if you set PRISMA_NEXT_* variables for the early prisma-next command, is on Environment variables.