Sentry-ruby: browser and OS reporting incorrect with 2.1.x

[dentarg]

I just switched a Sinatra application running on Heroku from using sentry-raven 1.2.2 to using sentry-raven 2.1.2 and now Sentry doesn't get the browser and OS versions correct, see this screenshot. The oldest event was created when the application was using sentry-raven 1.2.2.

Related to https://github.com/getsentry/raven-ruby/pull/560?

Please tell if you need more information on this

[nateberkopec]

@dentarg Sorry about that. Can you show me the code you're using to add browser/device/os context?

[dentarg]

I have no custom code for that, just "use Raven::Rack" in config.ru. Isn't that enough?

[StephaneRob]

Same pb with Rails

[dentarg]

@nateberkopec any ideas?

[nateberkopec]

Will take a look and fix this today 👍

[nateberkopec]

It looks like I misunderstood the docs for clients on this issue. If you just pass os, Sentry assumes that's the _browser's_ OS context, not the context of the server.

[nateberkopec]

For now, I'm just going to roll it back.

[nateberkopec]

Fixed in 2.1.3.

Sorry about this. Basically I misunderstood the Sentry client docs. :( We still report server information, but now do so in the proper place.

[StephaneRob]

thx @nateberkopec

[dentarg]

@nateberkopec thanks for the fix, but I don't really get why sentry-raven isn't reporting browser and OS anymore, see the first event at, it was created with sentry-raven 1.2.2 – it got both the browser and OS correct, I guess it took the info from the User-Agent header? why isn't sentry-raven 2.1 doing that?

[nateberkopec]

@dentarg Dammit, yup I'm seeing the same. Investigating.

[nateberkopec]

Something that I did is messing with the browser/OS auto-detection plugin in Sentry core. Trying to fix this ASAP but the Python people need to look at it and tell me where I'm messing up.

[nateberkopec]

Sorry about the confusion here. Difficult to debug behavior that's actually happening on the server end rather than in the client.

So the actual fix was to move the context out of contexts and into extra. This is only temporary, watch the linked Sentry core issue for the permanent solution.

This fix is available in 2.1.4, which should be available by the time you read this.

[dentarg]

Thanks! It now works as expected again:

[StephaneRob]

Thx @nateberkopec