Skip to content

Rails 404 errors incorrectly reported as 500 in transaction traces #2849

@dingsdax

Description

@dingsdax

When Rails serves public error pages for exceptions like RoutingError (404) or RecordNotFound (404), Sentry transaction traces incorrectly show http.response.status_code as 500 instead of the actual status code returned by Rails.

Metadata

Metadata

Assignees

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions