Transaction status incorrectly reports 500 (internal_error) instead of actual HTTP status code (eg. 404) when Rails handles exceptions

Aperta
#2,825 6 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

@sl0thentr0py ci sta già lavorando.

Dal 8/1/2026.

  • #2848 di @solnic — chiusa senza merge

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Bug Ruby sentry-rails Spans
Issue Description

When Rails handles an exception internally and converts it to a specific HTTP status code (e.g., ActiveRecord::RecordNotFound -> 404), the Sentry transaction is incorrectly reported with status internal_error and http.response.status_code: 500 instead of the actual HTTP response status code.

This creates inaccurate reports, as all Rails-rescued exceptions appear as 500 errors in Sentry, even though the client receives the correct HTTP status code (404, 422, etc.).

The breadcrumbs in the transaction correctly show the actual status code (404), but the transaction-level status and span-level status codes are incorrect (500).

Even though version 6.0.0+ includes trace_ignore_status_codes which by default excludes 404s from being traced, this is a workaround rather than a fix. The underlying issue of incorrect status code reporting remains for any status codes that are not ignored.

Reproduction Steps
  1. Configure a Rails application with sentry-rails version 5.27.0
  2. Enable tracing with config.traces_sample_rate = 1.0
  3. Create a route that raises ActiveRecord::RecordNotFound or similar exception that Rails rescues and converts to a 404 response
  4. Make a request to that route
  5. Examine the transaction in Sentry
Expected Behavior
  • Span status should be "not_found"
  • Span data.http.response.status_code should be 404
Actual Behavior
  • Span status is "internal_error"
  • Span data.http.response.status_code is 500
Ruby Version

Ruby 3.4.4

SDK Version

sentry-ruby: 5.27.0

Integration and Its Version

No response

Sentry Config

No response

Lingua principale
Ruby
Stelle
990
Fork
552
Merge medio
2g 16h
PR unite (30g)
29

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di getsentry/sentry-ruby

Tutte le issue di getsentry/sentry-ruby

Issue simili

Altre issue su Ruby

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.