You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ActiveSupport from Rails 6.0.6 seems to handle request status the same way as Rails 5.x, so the payload from subscribe_to_event doesn't have the request status on it, leading to unknown statuses for Sentry transactions.
I change the condition on abstract_subscriber.rb file from
if ::Rails.version.to_i == 5
to:
if ::Rails.version.to_f < 6.1
and it properly set the request status.
I can open a PR with this fix.
Reproduction Steps
Install Rails 6.0.6 and add a debugger on subscribe_to_event method in the abstract_subscriber.rb file. The method for Rails 5.x works with Rails 6.0.6 as expected adding the :status to the payload, and the other one leave :status as nil.
Expected Behavior
Request status is present in the event payload and also on Sentry breadcrumbs.
Actual Behavior
Request status is calculated as 0 and Sentry dashboard show transaction as unknown status.
Issue Description
ActiveSupport
from Rails 6.0.6 seems to handle request status the same way as Rails 5.x, so thepayload
fromsubscribe_to_event
doesn't have the request status on it, leading tounknown
statuses for Sentry transactions.I change the condition on
abstract_subscriber.rb
file fromto:
and it properly set the request status.
I can open a PR with this fix.
Reproduction Steps
Install Rails 6.0.6 and add a debugger on
subscribe_to_event
method in theabstract_subscriber.rb
file. The method for Rails 5.x works with Rails 6.0.6 as expected adding the:status
to thepayload
, and the other one leave:status
asnil
.Expected Behavior
Request status is present in the event payload and also on Sentry breadcrumbs.
Actual Behavior
Request status is calculated as
0
and Sentry dashboard show transaction asunknown
status.Ruby Version
2.7.2
SDK Version
5.7.0
Integration and Its Version
Rails
Sentry Config
The text was updated successfully, but these errors were encountered: