Skip to content
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.TelemetryUmbilical.document.md)

Direct Sharing URL

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

Telemetry Umbilical; Migrating, splicing, and filtering your telemetry

Talking Points

  1. Two Types of Telemetry {file, streaming}
  2. All telemetry for a partition {container, VM, or Host} must only use 2x sockets - multiple apps need to be aggregated / multiplexed
  3. The 'umbilical' is a choke point; that has standard 'pipe fittings'
  4. The umbilical can be 'cut' and rerouted - such that there are only two locations per 'partition' {container, VM, Host} to be cut, should (re)routing, filtering, need to occur