-
-
Notifications
You must be signed in to change notification settings - Fork 485
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replicate Raven.capture using sentry-ruby #1267
Comments
For anyone else reading this, the best way I've found to do this so far is:
And specific to using this is in AWS Lambda, I also found that I had to disable the default asynchronous sending to get it to work – presumably this is because the Lambda function would exit before my Sentry error was able to be logged, but I didn't spend the time to confirm the cause.
Docs: https://github.com/getsentry/sentry-ruby#blocking-vs-non-blocking |
thanks for reporting this and provide an example. but to keep |
Release 5.4.0 includes |
Describe the bug
Hello, I'm trying to migrate from
sentry-raven
tosentry-ruby
, but I haven't been able to figure out how to replicate this behaviour:https://github.com/getsentry/sentry-ruby/tree/master/sentry-raven#usage
It seems that there is not an equivalent
Sentry.capture
method and I couldn't find it in the migration guide.I'm using this in a Ruby AWS Lambda function, which is why I'm looking to use a capture block to essentially wrap my entire application code, rather than being able to use something like the rails integration.
Is anyone able to provide some guidance? Thanks!
To Reproduce
Expected behavior
Capture the exception.
Actual behavior
Environment
sentry-ruby 4.2.0
Raven Config
The text was updated successfully, but these errors were encountered: