review · segments
Sentry integration research for auctionbot (L9) from lounge (L11) reference
pi 117 events 1 segments
segment 1 of 1
Produce Sentry integration findings spec for auctionbot from lounge reference
Attempted to read Solo scratchpad 591 via MCP but it was unavailable; proceeded with manual research comparing lounge's Sentry configuration (sentry/sentry-laravel ^4.25, Laravel 11 wiring via bootstrap/app.php) with auctionbot's Laravel 9 setup. Key findings: sentry-laravel ^4.25 supports Laravel 9 (illuminate/support ^6..^13); L9 exception wiring uses app/Exceptions/Handler.php::register with Integration::captureUnhandledException instead of Integration::handles; Flare/Ignition currently installed must be reconciled; the 'sentry' log channel should not be in the default stack to avoid double reporting. Wrote full findings (12 sections) to /tmp/sentry-findings.md.
outcome
Written to /tmp/sentry-findings.md containing complete spec (sections 1-12) covering package install, exception wiring, log channel config, SENTRY_* env keys, Horizon queue failures, and deploy guard migration.
next steps
- Review the findings file for completeness and correctness
- Proceed with implementation phase: install package, configure DSN, wire Handler, add log channel, set up Horizon failure handling
- Update todo 314 when Solo MCP is available
key decisions
- Use sentry/sentry-laravel ^4.25 — version compatibility confirmed for Laravel 9
- Exception wiring for L9 must use app/Exceptions/Handler.php::register() with Integration::captureUnhandledException(), not bootstrap/app.php
- Flare/Ignition decision deferred; either remove Flare or keep both with stack reconfiguration
- Defer lounge's Sentry mirror, triage worker, and admin UI to Phase 2
open questions
- Should Flare/Ignition be removed entirely or kept alongside Sentry with separate log stacks?
- Should the 'sentry' log channel be added to the default stack (with risk of double reporting) or only used explicitly via Log::channel('sentry')?
- What value should be used for SENTRY_TRACES_SAMPLE_RATE_QUEUE given auctionbot's heavy queue workload?
1 month ago → 1 month ago