Skip to content

Add more telemetry for progression graph query commands to help better understand usage patterns #78202

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

Merged

Conversation

ToddGrun
Copy link
Contributor

This will help us understand better which commands are being used and the efforts we should expend to continue supporting certain commands if we move from the progression APIs to IAttachedCollectionSourceProvider.

@ToddGrun ToddGrun requested a review from a team as a code owner April 18, 2025 15:18
@ghost ghost added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels Apr 18, 2025
@arunchndr
Copy link
Contributor

@ToddGrun can we please cherry pick to 17.14 when you get a chance?

@ToddGrun
Copy link
Contributor Author

can we please cherry pick to 17.14 when you get a chance?

#78203

@@ -18,6 +19,8 @@ internal sealed partial class SearchGraphQuery(
{
public async Task<GraphBuilder> GetGraphAsync(Solution solution, IGraphContext context, CancellationToken cancellationToken)
{
using var _ = Logger.LogBlock(FunctionId.GraphQuery_Search, KeyValueLogMessage.Create(LogType.UserAction), cancellationToken);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this LogType.UserAction mean we'll actually get a telemetry event created?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cyrus asked something similar in the 17.14 PR. LogType doesn't seem to matter for telemetry, but this defaults the logLevel to LogLevel.Information. The telemetry logger ignores message with LogLevel < LogLevel.Information

@arunchndr arunchndr merged commit 37a6dff into dotnet:main Apr 18, 2025
25 checks passed
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Apr 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead VSCode
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants