Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add debugger telemetry

Open
#3,092 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby
Domain
devtools, observability

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.

Description

pinned vscode

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.

Dominant language
Ruby
Stars
2k
Forks
281
Avg merge
1h 47m
Merged PRs (30d)
8

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Shopify/ruby-lsp

All issues in Shopify/ruby-lsp

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.