Log Framework name to more Windows ML relevant events by angelser · Pull Request #27256 · microsoft/onnxruntime
and others added 2 commits
February 5, 2026 10:36
angelser
marked this pull request as ready for review
angelser
deleted the
user/angelser/telemetrytweaks
branch
tianleiwu pushed a commit that referenced this pull request
Feb 12, 2026This PR adds the frameworkName field to critical Windows ML telemetry events to ensure proper event attribution and prevent data loss. The frameworkName field is added to ensure that Windows ML events are not lost and do not require joins with events that might have been emitted outside the scope of the time span the processing scripts check for long-running apps/processes. This allows each event to be self-contained with framework identification. The following telemetry events now include the frameworkName field: 1. **SessionCreationStart** - Logs when session creation begins 2. **SessionCreation** - Logs session creation details including model metadata 3. **RuntimeError** - Logs runtime errors (both DEBUG and release builds) 4. **RuntimePerf** - Logs runtime performance metrics including total runs and duration 5. **AutoEpSelection** - Logs automatic execution provider selection policy and results 6. **ProviderOptions** - Logs execution provider configuration options All events now include TraceLoggingString(ORT_CALLER_FRAMEWORK, "frameworkName") to maintain consistent framework identification across the telemetry pipeline. --------- Co-authored-by: Angela Serrano Brummett <angelser@microsoft.com>
tianleiwu added a commit that referenced this pull request
Feb 13, 2026This cherry-picks the following commits for the 1.24.2 release: - #27096 - #27077 - #26677 - #27238 - #27213 - #27256 - #27278 - #27275 - #27276 - #27216 - #27271 - #27299 - #27294 - #27266 - #27176 - #27126 - #27252 --------- Co-authored-by: Xiaofei Han <xiaofeihan@microsoft.com> Co-authored-by: Jiajia Qin <jiajiaqin@microsoft.com> Co-authored-by: Yulong Wang <7679871+fs-eire@users.noreply.github.com> Co-authored-by: qti-monumeen <monumeen@qti.qualcomm.com> Co-authored-by: Ankit Maheshkar <ankit.maheshkar@intel.com> Co-authored-by: Eric Crawford <eric.r.crawford@intel.com> Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com> Co-authored-by: guschmue <22941064+guschmue@users.noreply.github.com> Co-authored-by: Guenther Schmuelling <guschmue@microsoft.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: angelser <32746004+angelser@users.noreply.github.com> Co-authored-by: Angela Serrano Brummett <angelser@microsoft.com> Co-authored-by: Misha Chornyi <99709299+mc-nv@users.noreply.github.com> Co-authored-by: hariharans29 <9969784+hariharans29@users.noreply.github.com> Co-authored-by: eserscor <erscor@microsoft.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Baiju Meswani <bmeswani@microsoft.com> Co-authored-by: Adrian Lizarraga <adlizarraga@microsoft.com> Co-authored-by: Ti-Tai Wang <titaiwang@microsoft.com> Co-authored-by: bmehta001 <bmehta001@users.noreply.github.com>
adrastogi pushed a commit that referenced this pull request
Feb 13, 2026This PR adds the frameworkName field to critical Windows ML telemetry events to ensure proper event attribution and prevent data loss. The frameworkName field is added to ensure that Windows ML events are not lost and do not require joins with events that might have been emitted outside the scope of the time span the processing scripts check for long-running apps/processes. This allows each event to be self-contained with framework identification. The following telemetry events now include the frameworkName field: 1. **SessionCreationStart** - Logs when session creation begins 2. **SessionCreation** - Logs session creation details including model metadata 3. **RuntimeError** - Logs runtime errors (both DEBUG and release builds) 4. **RuntimePerf** - Logs runtime performance metrics including total runs and duration 5. **AutoEpSelection** - Logs automatic execution provider selection policy and results 6. **ProviderOptions** - Logs execution provider configuration options All events now include TraceLoggingString(ORT_CALLER_FRAMEWORK, "frameworkName") to maintain consistent framework identification across the telemetry pipeline. --------- Co-authored-by: Angela Serrano Brummett <angelser@microsoft.com>
adrastogi pushed a commit that referenced this pull request
Feb 16, 2026This PR adds the frameworkName field to critical Windows ML telemetry events to ensure proper event attribution and prevent data loss. ## Reason The frameworkName field is added to ensure that Windows ML events are not lost and do not require joins with events that might have been emitted outside the scope of the time span the processing scripts check for long-running apps/processes. This allows each event to be self-contained with framework identification. ## Events Modified The following telemetry events now include the frameworkName field: 1. **SessionCreationStart** - Logs when session creation begins 2. **SessionCreation** - Logs session creation details including model metadata 3. **RuntimeError** - Logs runtime errors (both DEBUG and release builds) 4. **RuntimePerf** - Logs runtime performance metrics including total runs and duration 5. **AutoEpSelection** - Logs automatic execution provider selection policy and results 6. **ProviderOptions** - Logs execution provider configuration options All events now include TraceLoggingString(ORT_CALLER_FRAMEWORK, "frameworkName") to maintain consistent framework identification across the telemetry pipeline. --------- Co-authored-by: Angela Serrano Brummett <angelser@microsoft.com>
adrastogi added a commit that referenced this pull request
Feb 19, 2026This cherry-picks the following commits for the release: - #27252 Record service in telemetry events - #27256 Log Framework name to more Windows ML relevant events --------- Co-authored-by: bmehta001 <bmehta001@users.noreply.github.com> Co-authored-by: angelser <32746004+angelser@users.noreply.github.com> Co-authored-by: Angela Serrano Brummett <angelser@microsoft.com> Co-authored-by: Aditya Rastogi <adityar@ntdev.microsoft.com>
This was referenced
Feb 23, 2026This was referenced
Feb 23, 2026This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters