Ruby/Rails logs onboarding suggests removed enable_logs
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- rails, react, ruby, typescript
- Domain
- documentation
Research direction
Start with static/app/gettingStartedDocs/ruby-rails/onboarding.tsx, ruby/onboarding.tsx, and ruby/logs.tsx, comparing their snippets with sentry-ruby 7.x behavior. Remove the config.enable_logs = true guidance and update the version note and structured logging guidance to match 7.0.0/7.1.0 changes. Done means the Ruby and Rails onboarding snippets no longer show the removed option and the logs copy reflects current 7.x setup.
Written by the indexing model from the issue text.
Description
The Ruby and Rails onboarding snippets tell users to set config.enable_logs = true. sentry-ruby removed that option in 7.0.0, so on current SDK versions (7.x, latest 7.2.0) the snippet raises NoMethodError in Sentry.init. Reported by a customer setting up Rails with sentry-ruby 7.2.0.
Affected onboarding code (pinned to f182595):
ruby-rails/onboarding.tsxL24–30: added when Logs is selectedruby/onboarding.tsxL22–28: same snippet for plain Rubyruby/logs.tsxL22–68: logs onboarding used by Ruby and Rails. The copy says to setenable_logs, the sample sets it, and the version note only mentions5.24.0 or higher
SDK changes behind this:
- 7.0.0, getsentry/sentry-ruby#3053: logs are enabled by default and
enable_logsis removed. No compatibility shim remains - 7.1.0, getsentry/sentry-ruby#3102: Rails structured logging is off by default. Turn it on with
config.rails.structured_logging.enabled = true
Workaround: drop the config.enable_logs = true line.
Open question: whether config.enabled_patches = [:logger] is still the recommended setup on 7.x.
cc @getsentry/value-discovery (CODEOWNERS for gettingStartedDocs) @sl0thentr0py (sentry-ruby)
via @danielsheccoury-sentry.
--
- Dominant language
- Python
- Stars
- 45.7k
- Forks
- 5k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 642
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from getsentry/sentry
-
Tag keys like os.name are auto-linked as domains in issue alert emailsPossibly taken @ashrafulX claimed this 6 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getsentry/sentry#129182 · 1 comment ·
Maintainers usually reply within 1 day
-
find_referenced_groups: Fixes-keyword ID list spans newlines, linking wrong issues as fixedPossibly taken @CodeAlex52 claimed this 42 days ago. OpenProduct Area: Releases Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
getsentry/sentry#125575 · 3 comments ·
Maintainers usually reply within 1 day
-
Cocoa replays hide Logs tab on supported SDK versionsPossibly taken @Brian-An claimed this 32 days ago. OpenBug Cocoa Replays
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
getsentry/sentry#124217 · 1 comment ·
Maintainers usually reply within 1 day
-
Product Area: Settings - Auth Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
getsentry/sentry#122437 · 6 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Incorrect Russian translation in django.poPossibly taken @nightcityblade claimed this 28 days ago. OpenBug Good First Issue Product Area: Settings - Integrations
Difficulty 1/5 Under an hour Newbie friendliness 90/100
getsentry/sentry#120651 · 3 comments ·
Maintainers usually reply within 1 day
All issues in getsentry/sentry
Similar issues
-
release
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
MichaelYcJo/SpecSeal#1535 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
valentinfrlch/ha-llmvision#769 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 75/100
daniel-ospina/tortoise#11937 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue help wanted python up-for-grabs
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
andrewsiah/agentswarm-data-tasks#238 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
cadence-workflow/cadence-ai-samples#175 ·
Maintainers usually reply within 1 day