Repository navigation
remove file opt-out from telemetery and only use environment variable #6078
Description
We should only have one opt-out mechanism. We should remove the file opt-out as it is not flexible enough for all situations.
{{ message }}
We should only have one opt-out mechanism. We should remove the file opt-out as it is not flexible enough for all situations.
Activity
daxian-dbw commentedon Feb 1, 2018
I agree that we should only have one way to opt-out. If .NET Core uses the environment variable only, then we should do the same.
iSazonov commentedon Feb 1, 2018
I agree - we should not litter the home folder.
I'd also cosider Enterprises - I believe they want use GPO for Windows. Most MSFT products have such registry keys to turn on/off telemetry.
thezim commentedon Feb 1, 2018
Is opting out an option during the install now? Personally I would prefer to have to opt in.
Ilya (@iSazonov) environment variables are stored in the in registry so this shouldn't be an issue.
My only concern that users can typically override system environment variables with there user environment variables in controlled enterprises. Only looking for variables value may allow users to override system level policy for telemetry.
iSazonov commentedon Feb 2, 2018
Greg Zimmerman (@thezim)
We can set environment variable by GPP but security men require forced security policy.
SteveL-MSFT commentedon Feb 2, 2018
Let's be clear that any new telemetry will likely be opt-in and be described in a RFC. The current basic startup telemetry we have now helps provide data of PSCore6 adoption and determines if we increase or decrease our investments. Since we ship packages outside of GitHub, we can't just track download numbers (which are unreliable anyways).