Sinatra Error and Performance Monitoring
Sinatra Actionable insights to resolve Sinatra performance bottlenecks and errors. Improve your Sinatra monitoring workflow with a full view of releases so you can mark errors as resolved and prioritize live issues.
Getting Started is Simple
Grab the Sentry Ruby SDK:
gem "sentry-ruby"
Configure your DSN:
require 'sentry-ruby' Sentry.init do |config| config.dsn = 'https://<key>@sentry.io/<project>' config.breadcrumbs_logger = [:sentry_logger, :http_logger] # To activate Tracing, set one of these options. # We recommend adjusting the value in production: config.traces_sample_rate = 1.0 # or config.traces_sampler = lambda do |context| 0.5 end end
Check our documentation for the latest instructions.
See all platforms
Sinatra Performance Monitoring
Quickly identify Sinatra performance issues and view full end-to-end distributed trace to see the exact, poor-performing API call and surface any related errors.
Sinatra Monitoring with Complete Stack Traces
Take advantage of built-in integrations with Rails, Sidekiq, DelayedJob, and more of your favorite RubyGems. Enable asynchronous reporting so errors are logged quickly in a background job. Filter and group Sinatra exceptions intuitively to eliminate noise.
Fill In The Blanks About Sinatra Errors
Expose important events that led to each Sinatra exception: a string to label where the event took place, message, timestamp. Learn in which version a bug first appeared, merge duplicates, and know if things regress in a future release.
“Sentry has become mission-critical to the way we build and ship software.”
See the Full Picture of Any Sinatra Exception
Get the user’s unique id, contact info, and IP address, as well as any localization as context to resolve the error and notify your customer.
Index and aggregate tags to easily search your error reports, see the distribution of issues, and find what’s a priority or a trend.
Find answers to key questions: Is the Sinatra exception limited to a single server? What arguments caused the ActiveJob to fail?
It’s why companies that don’t have a complete view of their infrastructure are being punished:
The average cost of network downtime is around $5,600 per minute — or $300,000 per hour.
1 out of 5 online shoppers will abandon their cart because the transaction process was too slow.
On average, a two-second slowdown in page load decreases revenues by 4.3 percent.