Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create centralized infrastructure and UX for enabling extension telemetry #3316

Open
adrastogi opened this issue Jun 27, 2024 · 1 comment
Open
Labels
Issue-Feature New feature or request Type-Telemetry

Comments

@adrastogi
Copy link
Contributor

Suggested new feature or improvement

Dev Home should have APIs and UI (e.g., end-user control mechanisms) for helping manage any data collection done by extensions.

Scenario

Extension authors may have a need to log diagnostics to better understand the usage and health of their extensions. Rather than having each extension implement their own solutions for things like managing user opt-in / out-out, it'd be better to have Dev Home provide a common pattern for this. (Folks implementing extensions could then choose whatever technology option they want- but at least this aspect of the experience would be consistent.)

Additional details

A motivating use case here is for Quickstart Playground. We get some level of diagnostics from Dev Home directly, but there are more detailed pieces of data we'd want to report from the Azure extension (that reporting would be unblocked by this feature).

@adrastogi adrastogi added the Issue-Feature New feature or request label Jun 27, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage New issue that the core contributors need to triage label Jun 27, 2024
@cinnamon-msft cinnamon-msft removed the Needs-Triage New issue that the core contributors need to triage label Jul 9, 2024
@MattHyman
Copy link
Member

MattHyman commented Jul 25, 2024

The Microsoft Game Dev Extension is also interested in this functionality; a possible model that can be followed would be how VS code handles extension telemetry. This includes VS code having a main setting the extensions must respect if it disables telemetry.

Ideally there would be documentation on what extensions should offer regarding telemetry opt out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature New feature or request Type-Telemetry
Projects
None yet
Development

No branches or pull requests

4 participants