-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Update .NET SDK and .NET CLI telemetry about collecting data for mobile and WebAssembly workloads #39276
Comments
I am not sure about setting the right labels, so please feel free to select the correct ones. |
Hey @tdykstra you addressed me to this issue. To be honest, I'm not exactly sure how to do this correctly. But, I tried my best with https://github.com/dotnet/docs/compare/main...timdeschryver:issue/39276?expand=1. I also suppose the additional property added in dotnet/runtime#90950 needs to be documented. |
@ivanpovazan @steveisok I'm not sure how to translate the code in dotnet/runtime#90208 and dotnet/runtime#90950 to the table in the doc. @timdeschryver made a proposed update that you can see here. Is this correct? If not, can you please update a couple of data points in the table to show us how to interpret the code? And likewise if any data points from dotnet/runtime#90208 were missed in the proposed table changes. |
Hello, I would suggest opening a PR so it would be easier to review the changes and comment/align with what has been introduced in: dotnet/runtime#90208 and dotnet/runtime#90950 |
Sounds good! |
In .NET8, with dotnet/runtime#90208 we introduced telemetry for collecting data about mobile and WebAssembly workloads.
This change should also be documented in https://github.com/dotnet/docs/blob/e234edcaae55e45e93fbb4931a7ae70f16789f6d/docs/core/tools/telemetry.md by updating adequate tables in
Data points
section.cc: @steveisok @vitek-karas @baronfel
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
Associated WorkItem - 251070
The text was updated successfully, but these errors were encountered: