Skip to content

Split WSLCCreateSession event - #41327

Open
Craig Loewen (craigloewen-msft) wants to merge 1 commit into
masterfrom
user/crloewen/wslcsession-event-split
Open

Split WSLCCreateSession event#41327
Craig Loewen (craigloewen-msft) wants to merge 1 commit into
masterfrom
user/crloewen/wslcsession-event-split

Conversation

@craigloewen-msft

Copy link
Copy Markdown
Member

Summary of the Pull Request

Split the WSLCCreateSessionEvent's CallerInfo to its own event for easier filtering

PR Checklist

  • Closes: Link to issue #xxx
  • Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
  • Tests: Added/updated if needed and all pass
  • Localization: All end user facing strings can be localized
  • Dev docs: Added/updated if needed
  • Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Small change to split the event.

Validation Steps Performed

Clang format and compiling.

Copilot AI lite review requested due to automatic review settings August 12, 2026 17:38

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates WSL service telemetry in WSLCSessionManagerImpl::CreateSession to split the caller image name out of the existing session-creation event into a dedicated event, enabling easier filtering by caller information.

Changes:

  • Ends the existing WSLCCreateSession TraceLogging event before emitting caller-related data.
  • Adds a new WSLCCreateSessionCaller TraceLogging event that contains CallerFileName.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +367 to 372
WSL_LOG(
"WSLCCreateSessionCaller",
TelemetryPrivacyDataTag(PDT_ProductAndServiceUsage),
TraceLoggingKeyword(MICROSOFT_KEYWORD_CRITICAL_DATA),
TraceLoggingValue(callerFileName.c_str(), "CallerFileName"),
TraceLoggingLevel(WINEVENT_LEVEL_INFO));
@benhillis

Copy link
Copy Markdown
Member

I don't have the full context I guess, but why are two events preferable to one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants