Rack Middleware
Using a framework?
Check out the other SDKs we support in the left-hand dropdown.
In addition to capturing errors, you can monitor interactions between multiple services or applications by enabling tracing. You can also collect and analyze performance profiles from real users with profiling.
Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below.
Add the sentry-ruby gem to your Gemfile:
Gemfilegem "sentry-ruby"
Add the sentry-ruby and stackprof gems to your Gemfile:
Gemfilegem "stackprof"
gem "sentry-ruby"
Configuration should happen as early as possible in your application's lifecycle.
Add use Sentry::Rack::CaptureExceptions to your config.ru or other rackup file:
config.rurequire 'sentry-ruby'
Sentry.init do |config|
config.dsn = 'https://examplePublicKey@o0.ingest.sentry.io/0'
# get breadcrumbs from logs
config.breadcrumbs_logger = [:sentry_logger, :http_logger]
# enable tracing
# we recommend adjusting this value in production
config.traces_sample_rate = 1.0
# enable profiling
# this is relative to traces_sample_rate
config.profiles_sample_rate = 1.0
end
use Sentry::Rack::CaptureExceptions
If you're not using Rackup to run your app, then Sentry initialization code must be placed before your code requires Sinatra:
app.rbrequire 'sentry-ruby'
Sentry.init do |config|
config.dsn = 'https://examplePublicKey@o0.ingest.sentry.io/0'
# get breadcrumbs from logs
config.breadcrumbs_logger = [:sentry_logger, :http_logger]
# enable tracing
# we recommend adjusting this value in production
config.traces_sample_rate = 1.0
# enable profiling
# this is relative to traces_sample_rate
config.profiles_sample_rate = 1.0
end
# in a non-rackup environment you must initialize the Sentry SDK before requiring sinatra
require 'sinatra'
use Sentry::Rack::CaptureExceptions
get "/" do
raise "foo"
end
This snippet includes an intentional error, so you can test that everything is working as soon as you set it up.
Sentry.capture_message("test message")
Learn more about manually capturing an error or message in our Usage documentation.
To view and resolve the recorded error, log into sentry.io and select your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").