Skip to content
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

Support for telemetry/event notification #21

Closed
maxandersen opened this issue Jul 6, 2016 · 3 comments · Fixed by #1992
Closed

Support for telemetry/event notification #21

maxandersen opened this issue Jul 6, 2016 · 3 comments · Fixed by #1992

Comments

@maxandersen
Copy link

maxandersen commented Jul 6, 2016

See https://github.com/Microsoft/language-server-protocol/blob/master/protocol.md#telemetry_event

@fbricon
Copy link
Contributor

fbricon commented Mar 27, 2017

which events do we want to report?
I assume we'd need to setup an event collection service at eclipse.org. Should we then make results public? oops, reporting would be logged on the client side

yaohaizh pushed a commit to yaohaizh/eclipse.jdt.ls that referenced this issue Jul 4, 2017
…es (eclipse-jdtls#22)

Signed-off-by: Fred Bricon <fbricon@gmail.com>
@rgrunber rgrunber self-assigned this Jul 7, 2021
@rgrunber
Copy link
Contributor

rgrunber commented Nov 19, 2021

Some possible information of interest :

  • Invisible/Maven/Gradle project on import
  • org.eclipse.jdt.core.compiler.source value for a project
  • "Size of Project" ? : LOC / # of Java source files / total size of JDT index files
  • unhandled exceptions
  • boolean/enum settings whose defaults are overridden (to determine if its worth changing default)
  • RTT for textDocument/completion or textDocument/codeAction, or if too much data, calculate a median RTT for the session
  • Time taken for project to be loaded (distinguish between first-time import)
  • How often certain commands / code actions are triggered

rgrunber referenced this issue in rgrunber/eclipse.jdt.ls Jan 20, 2022
- Fixes #21
- Disable by default, and require setting of java.telemetry.enabled
- Report build tool used for each project URI (eg. Maven, Gradle, etc.)
- Report JDT compiler source level (eg. 11)

Signed-off-by: Roland Grunberg <rgrunber@redhat.com>
rgrunber referenced this issue in rgrunber/eclipse.jdt.ls Jan 28, 2022
- Fixes #21
- Disable by default, and require setting of java.telemetry.enabled
- Report build tool used for each project URI (eg. Maven, Gradle, etc.)
- Report JDT compiler source level (eg. 11)

Signed-off-by: Roland Grunberg <rgrunber@redhat.com>
rgrunber referenced this issue in rgrunber/eclipse.jdt.ls Jan 28, 2022
- Fixes #21
- Disable by default, and require setting of java.telemetry.enabled
- Report build tool used for each project URI (eg. Maven, Gradle, etc.)
- Report JDT compiler source level (eg. 11)

Signed-off-by: Roland Grunberg <rgrunber@redhat.com>
@rgrunber
Copy link
Contributor

rgrunber commented Nov 2, 2022

Updated #21 (comment) based on some additional areas of interest.

@rgrunber rgrunber added this to the Early April 2023 milestone Mar 27, 2023
rgrunber added a commit that referenced this issue Mar 29, 2023
- Fixes #21
- Disable by default, and require setting of java.telemetry.enabled
- Report build tool used for each project URI (eg. Maven, Gradle, etc.)
- Report the lowest & highest JDT compiler source level (eg. 11, 17)
- Report whether the project(s) are being imported for the first time
- Report number of libraries & total size
- Report information about timing of various stages

Signed-off-by: Roland Grunberg <rgrunber@redhat.com>
@rgrunber rgrunber changed the title telemetry event Support for telemetry/event notification Mar 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants