We've experimented asking users on install or initial setup. But most of the time our tool runs in non interactive environments e.g. on a CI/CD set up (install and execution).
An additional flag for non-interactive installs can solve the problem, but that's a broken setup experience, someone has to look up the documentation after a failure to install.
Turning it off by default in case of a CI/CD setup means losing most of the data.
If you're setting up automated non-interactive installs, your job is to check for install failures and consult the documentation; I know that's part of my job.
I'd recommend a required installer flag forcing the user to make a decision, but I'm a user who generally leaves telemetry on.
Comments
We've experimented asking users on install or initial setup. But most of the time our tool runs in non interactive environments e.g. on a CI/CD set up (install and execution).
An additional flag for non-interactive installs can solve the problem, but that's a broken setup experience, someone has to look up the documentation after a failure to install.
Turning it off by default in case of a CI/CD setup means losing most of the data.
If you're setting up automated non-interactive installs, your job is to check for install failures and consult the documentation; I know that's part of my job.
I'd recommend a required installer flag forcing the user to make a decision, but I'm a user who generally leaves telemetry on.