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/Architecture.Action.Explanation.document.md)

Direct Sharing URL

http://microsoft.github.io/DynamicTelemetry/docs/Architecture.Action.Explanation.document/

Understanding Actions

Understanding an action in Dynamic Telemetry is crucial for grasping its workflows. An action involves diagnostic operations that do not alter system state and can be dynamically enabled or disabled using a provided program.

Unlike mitigation actions, these do not modify system state.

Examples of actions unsuitable for Dynamic Telemetry include restarting a service, rebooting a machine, writing to a file, or changing a config setting.

Suitable actions might involve enabling CPU sampling, which could impact performance but doesn't intentionally modify system state.

The following sections will discuss sample actions within the scope of Dynamic Telemetry, such as collecting configurations, enabling CPU sampling, managing Flight Recorders, inducing memory dumps, and collecting other state types.