-
Notifications
You must be signed in to change notification settings - Fork 30k
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
auto profiling telemetry tweak #164259
auto profiling telemetry tweak #164259
Conversation
reuse the same code to send the telemetry data for the renderer and the extension host send telemetry event without annotated stacktraces send fake error event with annotated stacktraces
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Telemetry stuff looks good, just the heads up about the error website
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry I missed this, we cannot have dynamic event names as it's impossible to classify what is being sent in the catalog
…log and send callers twice (annotated and not)
…n host profile analysis by that
logService.error(fakeError); | ||
|
||
// send telemetry event | ||
telemetryService.publicLog2<TelemetrySampleData, TelemetrySampleDataClassification>(`unresponsive.sample`, { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need for templated string here
reuse the same code to send the telemetry data for
the renderer and the extension host
send telemetry event without annotated stacktraces
send fake error event with annotated stacktraces
This is for #163819