User-Defined Errors — Complete Error Coverage Beyond 5xx

Every failure your team cares about now shows up in your error rates, issues, and alerts.

Hud already detects runtime errors automatically (HTTP 5xx, queue failures). But some failures don't look like errors from the outside: a request that returns 200 but the payment silently failed, a queue job that finishes but produces the wrong result. User-defined errors extend detection to cover these cases, based on your business logic.

What's New

• Mark any flow as failed from your code — Call setFailure() (Node) or set_failure() (Python) to mark a request or queue job as an error with a custom failure message. Hud counts it alongside HTTP 5xx in your endpoint and queue error rates.
• Issues with your failure message — User-defined errors create their own issues, titled with your message (e.g. "POST /checkout failed: payment provider timeout"). Each issue gets forensics, a timeline, and the same investigation tools as any other error issue.

How to Use Add a single SDK call wherever your code catches a failure that should be visible in Hud. In Node, for example: hud.setFailure("Payment failed"). Attach optional key-value context for added detail. See the full guide for setup and examples.

Supported SDKs

• Node.js 1.8.2+ — endpoints and queues
• Python 0.4.2+ — queues