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

Adding instrumentation to Azure toolsets to gather intelligence #3322

Closed
3 of 7 tasks
allenjzhang opened this issue May 10, 2024 · 2 comments
Closed
3 of 7 tasks

Adding instrumentation to Azure toolsets to gather intelligence #3322

allenjzhang opened this issue May 10, 2024 · 2 comments

Comments

@allenjzhang
Copy link
Member

allenjzhang commented May 10, 2024

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:

  • Privacy Review
  • New 1DS appID onboarding
  • Determine initial data set and source (emitter vs library)
  • Adding instrumentation

Checklist

  • Follow our Code of Conduct
  • Read the docs.
  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
@bterlson
Copy link
Member

Shouldn't this be in the Azure repo?

@allenjzhang
Copy link
Member Author

Moving to Azure repo. Azure/typespec-azure#828

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

No branches or pull requests

2 participants