Add debugger telemetry
Open
Nobody has claimed this yet.
pinned
vscode
- Dominant language
- Ruby
- Stars
- 2k
- Forks
- 281
- Avg merge
- 2h 14m
- Merged PRs (30d)
- 6
Description
We currently don't have telemetry about failures to launch the debugger or about its usage. It would be nice to instrument the debugger, so that we can improve our integrations.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or debugger entry points. Start by locating the debugger launch path and its usage lifecycle, then determine which failure and usage events are appropriate to instrument. Done means the agreed telemetry is implemented for both launch failures and debugger usage, with coverage for the relevant behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- devtools, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100