Rasputin

Runtime recorder

Optional. Adds arguments, returns, and call history to errors. Error reporting works without it.

How it works

During a request or job, Rasputin can record what your functions received and returned. That record is attached when the work fails.

Rasputin must instrument your functions to see those calls. Usually that means auto-instrumentation: run rasputin-instrument on compiled output, or use bun --preload … / node --import … when you run TypeScript directly.

See auto-instrumentation support before you change build or start scripts. If auto-instrumentation is not an option, see Instrumentation & executions for manual instrumentation and scoping.

What you need to set up

Two steps.

1. Instrument functions

Enable auto-instrumentation, or mark functions with execution.trace(). In production, run rasputin-instrument on compiled output.

2. Scope an execution

Wrap each request, job, or task with execution.createScope().

Where to go next

  1. Check auto-instrumentation support for your runtime and build.
  2. Follow Instrumentation & executions to instrument, scope work, and tune the recorder.