RedwoodJS collects completely anonymous telemetry data about general usage.
You can opt-out of sending this data at any time.
yarn redwood dev
, we gather
some anonymous usage data. When the process ends, we use a separate background process to send the data to our
telemetry database. There should be no performance impact on your CLI experience.
yarn create redwood-app
project setup utility, we also collect some anonymous usage data. This should have minimal impact on performance or your experience
when creating a new project. We send this data just before your new project is finished being created.
{
command: 'info', // the CLI command that was invoked
ci: false, // whether or not this is running in a CI environment
duration: 2353, // how long the process took, in milliseconds
NODE_ENV: 'development', // the value of NODE_ENV, if set
complexity: '4.1.2.6.3', // count of routes, prerendered, services, cells, and pages
system: '8.32', // cpu core count, memory in GB
sides: 'web,api', // sides that are in use
webBundler: 'webpack',
experiments: ['studio'], // any experimental features that are enabled
shell: 'zsh',
nodeVersion: '14.17.1',
yarnVersion: '14.17.1',
npmVersion: '14.17.1',
vsCodeVersion: '1.58.0',
redwoodVersion: '0.35.1',
os: 'macOS',
osVersion: '11.4',
}
yarn redwood build web --no-prerender
, we'll
record --no-prerender
. In addition to options, we also
collect anonymized error data.
yarn create redwood-app
utility, we gather data about the install options and performance; for example, TypeScript language target, initialize git, overwrite existing files, install node modules, and the duration of `yarn install` (if run). We also collect anonymized error data.
generate page GreatIdea
we would not record the GreatIdea
page name.
We do not collect any metrics which may contain sensitive data.
This includes, but is not limited to environment variables, file paths, contents of files, logs, or serialized JavaScript errors that have not been anonymized.
We believe you should be able to see exactly what data is being collected. Every time a Redwood CLI
command is run, the generated telemetry data is saved to a file within your project's .redwood/telemetry
directory.
These files contain the full payload sent to Redwood's telemetry database. Only the eight most recent files are retained.
.env
file, or anywhere
that creates variables for your user space, like .bashrc
or .bash_profile
:
REDWOOD_DISABLE_TELEMETRY=1
You can also use the --no-telemetry
flag
on any Redwood CLI command to disable telemetry during that one command.
In addition to the data files as described above, you can also view the telemetry background process logs. (This is a short-lived background process responsible for exporting generated data to Redwood's telemetry database.)
These logs are located at .redwood/logs/telemetry.out.log
and
.redwood/logs/telemetry.err.log
. They are overwritten each time
the telemetry background process is triggered.