Resque 'view' & API

luke.antins's Avatar


16 Oct, 2010 06:41 AM

Hey Guys,

I've put together a small failure backend for Resque that sends job exceptions to the API.
If your interested in taking a look, you can find it here: resque-exceptional

To make the job class/queue/job args information visible via the website, I've bundled it into the request parameters. Similar to how the Hoptoad failure backend does it.

I think it would be rather cool if:

  • The API could accept a 'resque' section of data. (not really needed, but would be cleaner imo?)
  • Have a different view of Resque failure data. Ability to view exceptions by queue for example could be useful.

While developing against your API I ran into a couple of issues:

  • Without sending ['application_environment']['env'] the errors didn't seem to show up. This isn't documented.
  • Unless you set a protocol_version param you'll get a 404 Not Found. Again, this isn't documented.
  • If my API Key is set, the API will ALWAYS return 200 OK, even if I don't send any data!!! Not helpful debugging why an error didn't show up in the web interface ;-)
  • The hash query param also isn't documented.
  • Along with the current JSON example, it would be useful to see one of the minimum JSON data required.

That's my two pence worth. Hopefully it contains some useful feedback? ;-)

Thanks! =)

  1. 1 Posted by Wal McConnell on 21 Oct, 2010 03:40 PM

    Wal McConnell's Avatar

    Hey Luke,

    Thanks again for your work.

    1. Having a resque view of error data would be great but its not in our short term plans at the moment. We'll keep it on our list though

    2. Thanks for spotting the application_environment/env. I've updated the docs at

    3. Yea the protocol version needs to be set because different protocol versions have differernt requirements in our API (for parsing and compression). Hence we require a protocol version.

    4. For scaleability reasons, processing of an API request is not done when the request is received by the API, it is merely 'accepted' and then queued for processing later. If processing that error fails later, then your right we have no way to highlight that. We could add a flag into the exceptional app if api requests are failing for a certain app, I'll think more about that.

    5. and 6, I'll update the API docs early next week to reflect this.

    thanks again,

  2. 2 Posted by Robert on 15 Feb, 2013 06:53 PM

    Robert's Avatar

    Hi, this is Robert with support, I am clearing out old tickets. If you are still having issues with this, send an email to [email blocked].


  3. Robert closed this discussion on 15 Feb, 2013 06:53 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac