5.1.1

Bug Fixes

• Allow overwriting of context values #1724
  • Fixes #1722
• Avoid duplicated capturing on the same exception object #1738
  • Fixes #1731

Refactoring

• Encapsulate extension helpers #1725
• Move rate limiting logic to each item in envelope #1742

5.1.0

Features

• Support for Redis #1697

  New breadcrumb logger: redis_logger

  When you opt in to the new redis_logger breadcrumbs logger:

  config.breadcrumbs_logger = [:redis_logger]

  The SDK now records a new db.redis.command breadcrumb whenever the Redis client is called. Attributes sent are
  commands, an array of each Redis command called with the attributes command and key, as well as server, which is
  the Redis server hostname, port and db number.

  Redis command spans

  Calls to Redis are also wrapped in a span called db.redis.command and if tracing is enabled will be reported to
  Sentry. The span description will be the command and key. e.g. "SET mykey". For transactions this will be in
  the format MULTI, SET mykey, INCR counter, EXEC.

• Sync activerecord, actionview and net-http span names #1681

• Support serializing ActiveRecord job arguments in global id form #1688

• Register Sentry's ErrorSubscriber for Rails 7.0+ apps #1705

  Users can now use the unified interfaces: Rails.error.handle or Rails.error.record to capture exceptions. See ActiveSupport::ErrorReporter for more information about this feature.

Bug Fixes

• Avoid causing NoMethodError for Sentry.* calls when the SDK is not inited #1713
  • Fixes #1706
• Transaction#finish should ignore the parent's sampling decision #1716
  • Fixes #1712
• Skip authorization header when send_default_pii is false #1717
  • Fixes #1714

5.0.2

• Respect port info provided in user's DSN #1702
  • Fixes #1699
• Capture transaction tags #1701
• Fix report_after_job_retries's decision logic #1704
  • Fixes #1698

5.0.1

• Don't reuse Net::HTTP objects in HTTPTransport #1696

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:

• #944
• #1424
• #1524

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:

1. 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

2. 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

Bug Fixes

• Directly execute ActionCable's action if the SDK is not initialized #1692
  • Fixes #1691

4.9.1

Bug Fixes

• Add workaround for ConnectionStub's missing interface #1686
  • Fixes #1685
• Don't initialize Event objects when they won't be sent #1687
  • Fixes #1683

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 using Net::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

• Minor improvements on Net::HTTP patch #1651
• Deprecate unnecessarily exposed attributes #1652
• Refactor Net::HTTP patch #1656
• Deprecate Event#configuration #1661
• Explicitly passing Rack related configurations #1662
• Refactor RequestInterface #1673

4.8.3

Bug Fixes

• Correctly return JobClass#perform's return value #1667
  • Fixes #1666

4.8.2

Documentation

• Rewrite documents with yard #1635

Bug Fixes

• Use prepended method instead of around_perform for ActiveJob integration #1631
  • Fixes #956 and #1629
• 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 and faraday will be removed from dependencies very soon.
    See this comment for more information about our plan to remove it.