What's the best way to provide extra_context for all Faraday::Error::ClientError?

[dblock]

Coming from artsy/doppler#136. Somewhere a Rails controller throws a Faraday::Error::ClientError. That gets logged with a generic to_s like "The server returned 400". We want the body of that response in Sentry.

What's the best way to accomplish that (customize what gets reported per type of StandardError) generically in a Rails app?

[nateberkopec]

Hiya @dblock!

The rescue_from block you posted in your issue there would work fine. You also sound like you might like this:

class Faraday::Error::ClientError
  def raven_context
    { :extra => { :response => response } } 
  end
end

See here.

[isaacseymour]

@nateberkopec would you be open to a PR doing this monkey-patching when this gem loads? Since sentry-raven depends on Faraday anyway, it seems helpful to add this context out-of-the-box to me.

[dblock]

+1 to what @isaacseymour is saying

[nateberkopec]

Hi, I don't maintain this anymore. Someone else does! I should probably remove my own owner status on rubygems.org too! 😅

[st0012]

sentry-raven is now in maintenance mode, so we won't introduce such change to it.
The new sentry-ruby doesn't support exception context anymore and we're planning to drop faraday soon. So we won't add the patch to it either 🙂