Skip to content
This repository was archived by the owner on Oct 2, 2021. It is now read-only.

Batch sending telemetry for some of the event notifications.#300

Merged
roblourens merged 2 commits intomicrosoft:masterfrom
changsi-an:master
Mar 7, 2018
Merged

Batch sending telemetry for some of the event notifications.#300
roblourens merged 2 commits intomicrosoft:masterfrom
changsi-an:master

Conversation

@changsi-an
Copy link
Contributor

Batch-sending telemetry is necessary because some notifications from debuggee might be too frequent for the telemetry infrastructure to handle. Take VS as an example, it throttles telemetry events if there are two many within a short period of time. We will lose some important telemetry when that happens.
The BatchTelemetryReporter will cache the received telemetry events and sends them out every 10 seconds.

This PR also refactors some code and migrates some general telemetry handling code from DebugSession.ts to utils.ts or telemetry.ts.

This PR also enables telemetry for debugger.paused and debugger.onScriptParsed notification events.

This PR retargets the change to master branch.

@roblourens roblourens merged commit b806895 into microsoft:master Mar 7, 2018
this._expectingStopReason = undefined;

smartStepP.then(should => {
await smartStepP.then(should => {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I add it to include the time spent in this operation in the overall measurement of onPaused event. Apart from the measurement function, no one seems to actively wait on the promise returned from this method.

@roblourens roblourens added this to the March 2018 milestone Apr 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants