Skip to content
This repository has been archived by the owner on Apr 14, 2022. It is now read-only.

Add telemetry for analysis time. #851

Closed
gramster opened this issue Apr 1, 2019 · 0 comments
Closed

Add telemetry for analysis time. #851

gramster opened this issue Apr 1, 2019 · 0 comments
Assignees
@jakebailey
Milestone
April 2019.1

Comments

@gramster
Copy link
Member

gramster commented Apr 1, 2019

As the title says, we should be gathering this in our telemetry so we can track improvements over time.
@jakebailey jakebailey self-assigned this Apr 2, 2019
@jakebailey jakebailey added this to the April 2019.1 milestone Apr 2, 2019
@jakebailey jakebailey mentioned this issue Apr 3, 2019
Merged
jakebailey added a commit that referenced this issue Apr 3, 2019
@jakebailey
Send telemetry event on analysis complete (#876)
59e3edf 
Closes #851.

Using the same definition of "complete" as the log message. If it did fewer than 100 items, then nothing is sent to prevent spamming for every small change. Open to suggestions for another arbitrary condition instead.

I'd include the system memory, but that'd require a bunch of code to make it work cross platform (or waiting for dotnet/corefx#22660).
jakebailey added a commit to jakebailey/python-language-server that referenced this issue Nov 1, 2019
@jakebailey
Send telemetry event on analysis complete (microsoft#876)
fb111d1 
Closes microsoft#851.

Using the same definition of "complete" as the log message. If it did fewer than 100 items, then nothing is sent to prevent spamming for every small change. Open to suggestions for another arbitrary condition instead.

I'd include the system memory, but that'd require a bunch of code to make it work cross platform (or waiting for dotnet/corefx#22660).
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jakebailey jakebailey

Labels
None yet
Projects
None yet
Milestone
April 2019.1
Development

No branches or pull requests
2 participants
@gramster @jakebailey