Dynamic Telemetry is a PROPOSAL : please provide feedback! :-)

Dynamic Telemetry is not an implementation, it's a request for collaboration, that will lead to an shared understanding, and hopefully one or more implementations.

Your feedback and suggestions on this document are highly encouraged!

Please:

1. Join us, by providing comments or feedback, in our Discussions page

2. Submit a PR with changes to this file ( docs/PositionPaper.ConfigurationDeployment.document.md)

Direct Sharing URL

http://microsoft.github.io/DynamicTelemetry/docs/PositionPaper.ConfigurationDeployment.document/

The Stresses and Risks behind simple 'Configuration' Deployment

Mechanisms

1. All PROBE's must be intentionally read-only

2. Configuration Code Review; two trained employees verify the PROBE will not collect unapproved information.

3. Ringed Deployment; instead of deploying to all machines, intantly, deploymens can be deployed slowly

4. 'Rip Cords'; near instant disablement in the case of emergency

Observer Effect

Observer Effect