← All platforms

Oban error tracking

Oban keeps the jobs moving. Keep the reasons they fail, too. The Sentry Oban integration sends their error reports to Telebugs on your server.

~/hoofnotes  nvim mix.exs config/config.exs
defp deps do
[
{:sentry, "~> 13.0"},
{:jason, "~> 1.4"},
{:finch, "~> 0.21"}
]
end
import Config
config :sentry,
# Copy the complete Telebugs DSN, key and path included.
dsn: "YOUR_TELEBUGS_DSN",
environment_name: config_env(),
integrations: [oban: [capture_errors: true]]
~/hoofnotes  mix deps.get
~/hoofnotes  iex -S mix

Hang on, I already use Sentry

Keep sentry and change its destination to your Telebugs DSN. Your error reports stay on your server. You don’t need a Sentry account.

Crashes or returned errors?

The Oban integration can report both job crashes and returned error results. You can filter expected failures in the SDK so they don’t crowd out the errors worth investigating.

Does this replace Oban’s job management?

No. Oban still queues, retries, and schedules jobs. Telebugs stores their error reports; this connection does not add cron check-in monitoring.