You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To support insights into internal service adoption and usage, we need to collect stats on active users. We do collect user information via VS Extension instrumentation. However, there seems to be anomalies in the user data collected. It would be reliable to directly collect from the TypeSpec toolset.
With that ask, TypeSpec Compiler with broader community usage would not be suitable to instrument. However for Azure toolset (autorest emitter, Azure.Core, ARM library), they can be instrumented to collect primarily internal user. The following is list of task breakdowns.
Tasks:
Privacy Review
New 1DS appID onboarding
Determine initial data set and source (emitter vs library)
Clear and concise description of the problem
To support insights into internal service adoption and usage, we need to collect stats on active users. We do collect user information via VS Extension instrumentation. However, there seems to be anomalies in the user data collected. It would be reliable to directly collect from the TypeSpec toolset.
With that ask, TypeSpec Compiler with broader community usage would not be suitable to instrument. However for Azure toolset (autorest emitter, Azure.Core, ARM library), they can be instrumented to collect primarily internal user. The following is list of task breakdowns.
Tasks:
Checklist
The text was updated successfully, but these errors were encountered: