Mention Sentry and AppSignal integration (#1062)

Mention Sentry and AppSignal integration in the README

README.md

@@ -827,7 +827,7 @@ metadata see docs for the `Oban.Telemetry` module.
 ### Reporting Errors
 
 Another great use of execution data is error reporting. Here is an example of
-integrating with [Sentry][sentry] to report job failures:
+integrating with [Honeybadger][honeybadger] to report job failures:
 
 ```elixir
 defmodule MyApp.ErrorReporter do
@@ -841,23 +841,22 @@ defmodule MyApp.ErrorReporter do
   end
 
   def handle_event([:oban, :job, :exception], measure, meta, _) do
-    extra =
-      meta.job
-      |> Map.take([:id, :args, :meta, :queue, :worker])
-      |> Map.merge(measure)
-
-    Sentry.capture_exception(meta.reason, stacktrace: meta.stacktrace, extra: extra)
+    Honeybadger.notify(meta.reason, stacktrace: meta.stacktrace)
   end
 end
 
 MyApp.ErrorReporter.attach()
 ```
 
-You can use exception events to send error reports to Honeybadger, Rollbar,
-AppSignal or any other application monitoring platform.
+You can use exception events to send error reports to Sentry, AppSignal, Honeybadger, Rollbar, or any other application monitoring platform.
+
+Some of these services support reporting Oban errors out of the box:
+
+  - Sentry — [Oban integration documentation](https://docs.sentry.io/platforms/elixir/integrations/oban)
+  - AppSignal - [Oban integration documentation](https://docs.appsignal.com/elixir/integrations/oban.html)
 
 [tele]: https://hexdocs.pm/telemetry
-[sentry]: https://sentry.io
+[honeybadger]: https://www.honeybadger.io
 
 ## Instance and Database Isolation