-
Notifications
You must be signed in to change notification settings - Fork 730
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
Telemetry Improvement: Create telemetry item for completion of a resource type #6329
Labels
Milestone
Comments
ghost
added
the
Needs: Triage 🔍
label
Mar 28, 2022
alex-frankel
added
devdiv
Related to Bicep tooling efforts in DevDiv
and removed
Needs: Triage 🔍
labels
Mar 30, 2022
The name of this event will be vscode-bicep/snippet/resourcetype |
Telemetry should include
Could also help the doc team with understanding the most authored resources and snippets |
ucheNkadiCode
added
the
P1
This is planned to be completed before the end of a release
label
May 31, 2022
ucheNkadiCode
changed the title
Telemetry improvement: Create telemetry item for completion of a resource name
Telemetry improvement: Create telemetry item for completion of a resource type
Jun 23, 2022
ucheNkadiCode
removed
the
P1
This is planned to be completed before the end of a release
label
Jun 23, 2022
ucheNkadiCode
changed the title
Telemetry improvement: Create telemetry item for completion of a resource type
Telemetry Improvement: Create telemetry item for completion of a resource type
Jun 28, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
In order to scope our problem to the most common resources #6249, it would be great to be able to track, what are the most common completions for "resource blah '_____'". This is the case where a user is trying to find the correct resource tag after they have named it.
Related to #6327
Partial Blocker for #6249
@StephenWeatherford has telemetry and information on ARM resources that are being used including version!
Are we able to get to the Azure backend telemetry and see what's actually being deployed?
The text was updated successfully, but these errors were encountered: