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/Architecture.Components.Observer.External.OffBox.document.md)

Direct Sharing URL

http://microsoft.github.io/DynamicTelemetry/docs/Architecture.Components.Observer.External.OffBox.document/

Offbox Processor Coming Soon

This processor has a unique characteristic of being off-box and separate from the machine being monitored. This is likely the least risky location to start the migration of dynamic telemetry. It acts as a filter or data shaper. Because it simply morphs telemetry after being produced, the machine producing it is unaware of its presence.

For example, this is a good location for initial security or privacy scrubbing. Tokens would be emitted from the machine but dropped prior to being ingested into a database.