-
Notifications
You must be signed in to change notification settings - Fork 728
Add telemetry for OmniSharp server requests #122
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
Conversation
ef3825c to
3f033aa
Compare
|
Sorry, that comment was supposed to be for the other PR. I haven't had a chance to look at this one yet. Give me a few minutes... |
| "windows": { | ||
| "program": "./coreclr-debug/debugAdapters/OpenDebugAD7.exe" | ||
| }, | ||
| "aiKey": "AIF-d9b70cd4-b9f9-4d70-929b-a071c400b217", |
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.
We need this. VS Code reads this value.
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.
It does? The instructions for VS Code telemetry do not say to add this to the debuggers section. Or, is this used for the debug adapter telemetry (which I'm totally unfamiliar with).
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.
Yes, it is used with debug adapter telemetry.
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.
OK -- will add that back. Sorry about that! I wasn't sure because the debugger code just dug it out of package.json.
|
👍 |
1. Add aiKey back into package.json for debug-adapter telemetry. In addition, to avoid duplicating the aiKey, the code that constructs a TelemetryReporter once again pulls the key from the package.json. 2. A couple of renames for clarity.
|
@gregg-miskelly I implemented your feedback. Look better now? |
|
👍 |
|
👍 |
This change adds telemetry tracking for the time elapsed from the point that a request sent to the OmniSharp server to the point that a response is received. To keep telemetry traffic low, we simply track the counts of various ranges of delay times for each type of request.
In addition, I refactored the telemetry a bit in coreclr-debug.ts to ensure that we can share the same TelemetryReporter.
cc @gregg-miskelly, @chuckries, @Pilchie