Telemetry Events vs. Inferred Activity

In telemetry collection, each event must represent a distinct and independent action within the system. Telemetry events should not be inferred from other related events or derived from backend logic. This approach ensures accuracy, transparency, and reliable tracking of system activities.

For example, actions such as _account modifications, scheduled task changes, or URL interactions need to be recorded as individual telemetry events. Relying on related events like process execution or network activity to infer these actions can lead to inaccuracies and gaps in data.

Each event should be captured directly by the telemetry system itself rather than inferred from other events. Properly categorizing and logging events ensures that telemetry data remains accurate, consistent, and easy to analyze.