Releases: getsentry/sentry-ruby
5.0.1
5.0.0
Breaking Change - Goodbye faraday
👋
TL;DR: If you are already on version 4.9
and do not use config.transport.http_adapter
and config.transport.faraday_builder
, you don't need to change anything.
This version removes the dependency of faraday and replaces related implementation with the Net::HTTP
standard library.
Why?
Since the old sentry-raven
SDK, we've been using faraday
as the HTTP client for years (see HTTPTransport). It's an amazing tool that saved us many work and allowed us to focus on SDK features.
But because many users also use faraday
themselves and have their own version requirements, managing this dependency has become harder over the past few years. Just to list a few related issues:
And with the release of faraday 2.0, we could only imagine it getting even more difficult (which it kind of did, see #1663).
So we think it's time to say goodbye to it with this release.
What's changed?
By default, the SDK used faraday
's net_http
adapter, which is also built on top of Net::HTTP
. So this change shouldn't impact most of the users.
The only noticeable changes are the removal of 2 faraday-specific transport configurations:
config.transport.http_adapter
config.transport.faraday_builder
If you are already on version 4.9
and do not use those configuration options, it'll be as simple as bundle update
.
What if I still want to use faraday
to send my events?
sentry-ruby
already allows users to set a custom transport class with:
Sentry.init do |config|
config.transport.transport_class = MyTransportClass
end
So to use a faraday-based transport, you can:
- Build a
FaradayTransport
like this:
require 'sentry/transport/http_transport'
require 'faraday'
class FaradayTransport < Sentry::HTTPTransport
attr_reader :adapter
def initialize(*args)
@adapter = :net_http
super
end
def send_data(data)
encoding = ""
if should_compress?(data)
data = Zlib.gzip(data)
encoding = GZIP_ENCODING
end
response = conn.post @endpoint do |req|
req.headers['Content-Type'] = CONTENT_TYPE
req.headers['Content-Encoding'] = encoding
req.headers['X-Sentry-Auth'] = generate_auth_header
req.body = data
end
if has_rate_limited_header?(response.headers)
handle_rate_limited_response(response.headers)
end
rescue Faraday::Error => e
error_info = e.message
if e.response
if e.response[:status] == 429
handle_rate_limited_response(e.response[:headers])
else
error_info += "\nbody: #{e.response[:body]}"
error_info += " Error in headers is: #{e.response[:headers]['x-sentry-error']}" if e.response[:headers]['x-sentry-error']
end
end
raise Sentry::ExternalError, error_info
end
private
def set_conn
server = @dsn.server
log_debug("Sentry HTTP Transport connecting to #{server}")
Faraday.new(server, :ssl => ssl_configuration, :proxy => @transport_configuration.proxy) do |builder|
builder.response :raise_error
builder.options.merge! faraday_opts
builder.headers[:user_agent] = "sentry-ruby/#{Sentry::VERSION}"
builder.adapter(*adapter)
end
end
def faraday_opts
[:timeout, :open_timeout].each_with_object({}) do |opt, memo|
memo[opt] = @transport_configuration.public_send(opt) if @transport_configuration.public_send(opt)
end
end
def ssl_configuration
{
verify: @transport_configuration.ssl_verification,
ca_file: @transport_configuration.ssl_ca_file
}.merge(@transport_configuration.ssl || {})
end
end
- Set
config.transport.transport = FaradayTransport
Please keep in mind that this may not work in the future when the SDK changes its HTTPTransport
implementation.
4.9.2
4.9.1
4.9.0
Features
- Add Action Cable exception capturing (Rails 6+) #1638
- Add request body & query string to
Net::HTTP
breadcrumb #1637
When config.send_default_pii
is set as true
, :http_logger
will include query string and request body in the breadcrumbs it logs.
- Add tracing support to
ActionCable
integration #1640
Bug Fixes
- Fix
Net::HTTP
breadcrump url when usingNet::HTTP.new
#1637 - Fix trace span creation when using
Net::HTTP.start
#1637 - Remove incorrect backtrace attribute from Event #1672
Documentation
- Document Transaction and Span classes #1653
- Document Client and Scope classes #1659
- Document Event and interface classes #1675
- Document TransactionEvent and breadcrumb-related classes #1676
- Use macro to avoid duplicated documentation #1677
Refactoring
4.8.3
4.8.2
Documentation
- Rewrite documents with yard #1635
Bug Fixes
- Use prepended method instead of
around_perform
forActiveJob
integration #1631 - Remove unnecessary ActiveJob inclusion #1655
- Lock faraday to version 1.x #1664
- This is a temporary effort to avoid dependency issue with
faraday 2.0
andfaraday
will be removed from dependencies very soon.
See this comment for more information about our plan to remove it.
- This is a temporary effort to avoid dependency issue with
4.8.1
4.8.0
Features
-
Support exception frame's local variable capturing
Example:
To enable this feature, you need to set
config.capture_exception_frame_locals
totrue
:Sentry.init do |config| config.capture_exception_frame_locals = true # default is false end
This feature should only introduce negligible performance overhead in most Ruby applications. But if you notice obvious performance regression, please file an issue and we'll investigate it.
-
Support
ActiveStorage
spans in tracing events #1588 -
Support
Sidekiq
Tags in Sentry #1596 -
Add Client Reports to collect dropped event statistics #1604
This feature reports statistics about dropped events along with sent events (so no additional requests made). It'll help Sentry improve SDKs and features like rate-limiting. This information will not be visible to users at the moment, but we're planning to add this information to user-facing UI.
If you don't want to send this data, you can opt-out by setting
config.send_client_reports = false
.
Bug Fixes
- Connect
Sidekiq
's transaction with its parent when possible #1590- Fixes #1586
- Use nil instead of false to disable callable settings #1594
- Avoid duplicated sampling on Transaction events #1601
- Remove verbose data from
#inspect
result #1602
Refactoring
- Move Sentry::Rails::CaptureExceptions before ActionDispatch::ShowExceptions #1608
- Refactor
Sentry::Configuration
#1595 - Tracing subscribers should be multi-event based #1587
Miscellaneous
- Start Testing Against Rails 7.0 #1581