Skip to content

environments: capture first integration decision inputs - #26201

Draft
Eleanor Boyd (eleanorjboyd) wants to merge 1 commit into
microsoft:mainfrom
eleanorjboyd:agents/kusto-data-integration-check
Draft

Eleanor Boyd (eleanorjboyd) wants to merge 1 commit into
microsoft:mainfrom
eleanorjboyd:agents/kusto-data-integration-check

Conversation

@eleanorjboyd

@eleanorjboyd Eleanor Boyd (eleanorjboyd) commented Oct 6, 2026 •

Copy link
Copy Markdown
Member

Summary

Add two optional boolean properties to the existing EDITOR.LOAD event:

  • envsAvailableAtDecision: whether Environments was visible in Python's extension host at the first cached integration decision.
  • envsEnabledAtDecision: the resolved python.useEnvironmentsExtension value at that decision.

Together these distinguish the availability and setting inputs behind usingEnvironmentsExtension, complementing the existing explicit-false scope telemetry.

Capture existing availability and resolved-setting inputs at the first cached integration decision and attach them passively to startup telemetry. Preserve decision timing, settings behavior, and event count; add GDPR metadata and regression coverage.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-changelog No news entry required skip-issue-check

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant