rb:trace

Trace request flow across Rails, Grape, and Sidekiq by statically analyzing entry points to map routes, controllers, services, models, and jobs into a concise step-by-step chain of file locations. It outputs a readable trace without executing code.

Debug a request execution path in Ruby on Rails by mapping the exact code route from the HTTP endpoint to the point where an unexpected value is introduced. It statically extracts arguments and identifies entry points like controllers, models, and cache writes.

Static analysis maps Sidekiq jobs and Grape APIs to file paths by detecting mounted API endpoints and background job entry points, then chaining the file locations to reveal where values change or side effects occur during execution.

You can trace a Ruby on Rails code path without running code because the trace is generated entirely through static analysis of entry points and argument extraction, producing a readable execution chain of file locations.

Find where a side effect occurs during a Grape API call by tracing the request execution path from the mounted API endpoint through services and models, generating a concise chain of file paths that illustrate the execution route.

The request flow tracer supports detecting cache writes and broadcasts as entry points, mapping them alongside routes, controllers, services, and models to produce a step-by-step trace of file locations.