New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
exq integration #54
Comments
I've had this discussion pop up a few other times about other background job libraries in Elixir. In general the problem I've noticed is that most of them are designed like Ruby libraries and not like Erlang/Elixir libraries. What I mean is that when an exception occurs they rescue it and do their cleanup. If they were to re-raise after cleanup then the process will crash and the error logger will be automatically notified. |
I confirmed that |
Two other notes on exq middleware --
|
@schneidmaster thanks! We'll keep an eye on the exq release so that we can potentially package an error-handling middleware with honeybadger. |
There are more than a handful of background job processors out there now: exq, verk, ecto_job, honeydew, kiq. There isn't an obvious favorite to support like there is with plug and phoenix. I don't believe it is tenable to support middleware for all of these projects inside of Honeybadger itself (not to mention how easy it is to integrate Honeybadger manually). @joshuap What do you think? Can we close this out? |
@sorentwo yep, thanks! |
This integration would automatically report exceptions from failed exq jobs, similar to how we do for Ruby/Sidekiq. See akira/exq#191 for a potential solution. We should also investigate if the current
use_logger
option already works for this case.The text was updated successfully, but these errors were encountered: