Skip to content

Laravel Dumps ​

Yerd can capture live Laravel telemetry - dump() / dd() output, database queries, queue jobs, rendered views, incoming requests, log writes, cache events, and outgoing HTTP calls - and stream it into a dedicated viewer in the desktop app, Herd-style. You see what your app is doing without sprinkling dd() everywhere or tailing log files.

Capture works through a native PHP extension (yerd-dump) that observes your app at the engine level, so your application needs no changes - no composer require, no service provider, no auto_prepend_file.

Off by default

Dump capture is disabled by default. Nothing is downloaded, loaded, or listening until you turn it on. See Enabling it below.

Requires a Laravel app (mostly)

Most categories - jobs, views, requests, logs, cache - are Laravel-specific. Dumps and database queries are framework-agnostic (queries are observed at the PDO level), so a plain PHP app still gets those. The richest experience is a Laravel app served through Yerd as a .test site.

In the desktop app ​

The fastest way to use Dumps is from the desktop app. Open the Dumps page under the Developer group in the side navigation.

The page lists captured requests, newest first: method, status, path, site, event count and duration. Pick one to see its events beside the list; in a narrow window the list becomes a table and a request opens in a drawer. While the newest request the list shows is selected, a newer one takes the selection as it arrives (a request hidden by the filter never does). If the daemon restarts, the list starts over with the new daemon's events.

  • The capture pill in the toolbar reads Intercepting on 2304 while capture is on, Paused while it is off, and Dump server stopped when the port can't be bound.
  • Pause / Resume turns interception off and on. Turning it on downloads or refreshes the extension and restarts your running PHP-FPM pools, so it can take a few seconds; pausing is instant.
  • Setup holds the Intercept dumps switch, the dump server address with Change port (the port lives in Settings ▸ Application Ports, default 2304), the eight captured signals (disabled until interception is on) and the per-PHP-version extension status, so you can see which installed versions have a matching yerd-dump build.
  • The open in window button pops the same list and detail out into the standalone Dumps window.
  • A request's detail has category chips with per-request counts, an event filter that narrows the events and the request list (it also matches a request's method, path and status), and a caller badge on each event: hover it for the project-relative path, click it to open the file in your default editor.

What you get ​

Captured events are grouped into categories, one per chip in a request's detail (the request summary heads the detail rather than getting a chip):

CategoryWhat it captures
Dumpsdump(), dd(), ddd() calls (rendered HTML + plain-text fallback)
QueriesEloquent / PDO database queries, with SQL, bindings, and timing
JobsDispatched queue jobs and their outcome (processing / processed / failed)
ViewsRendered Blade views and their bound data keys
RequestsA summary of each incoming HTTP request (method, URI, status, duration)
LogsLog writes, with level and context
CacheCache hits, misses, writes, and forgets
HTTPOutgoing HTTP client calls (curl / Guzzle / PSR-18)

Events are grouped by request, so you can see everything a single page load or job did together.

A log entry's context array is printed as indented JSON under its message, and entries with no context show just the level and message. Every context value is shown, including ones that aren't strings: numbers, booleans and null appear as text ("1", "true", "null"), and arrays and objects as their dump-style rendering.

Enabling it ​

Turn capture on from the Dumps view in the desktop app (in the side navigation). Enabling it does two things:

  1. Downloads the native extension. Yerd fetches the matching yerd-dump extension for each installed PHP version from the forjedio/yerd-php-ext releases, verifies it by SHA-256, and stores it alongside your PHP installs at {data}/php-ext/php-<version>/yerd-dump.so.
  2. Restarts your PHP-FPM pools so they load the extension.

After that, dumps flow into the viewer as you exercise your app.

Needs a matching released build

The extension is ABI-specific: there is one build per PHP minor, per OS, per architecture. If a build for your exact PHP version and platform hasn't been published yet, Yerd quietly skips that version - capture simply won't work for it until a matching .so ships. The Dumps view shows, per installed PHP version, whether a matching extension is present.

The download is best-effort: a network or verification failure is logged and leaves your sites running normally, just without capture. While capture is on, the daemon also checks for a newer yerd-dump release each time it starts and replaces any .so that no longer matches the published build.

No dumps on legacy PHP

Legacy PHP versions (7.4 / 8.0 / 8.1) never capture dumps - the yerd-dump extension isn't built for out-of-support PHP. The Dumps Setup dialog marks legacy versions "Too old: no dumps".

Category toggles are cheap

The extension reads a small state file at the start of every request and self-disables when capture is off, so pausing capture or flipping an individual category does not restart PHP. Turning capture back on does: each enable re-checks the extension and restarts your running pools.

Per-category toggles ​

Each category can be turned on or off independently from the Dumps Setup dialog. This is useful when one category is noisy (lots of queries on a busy page) or when you only care about one signal.

The outgoing HTTP category is off by default even when capture is enabled

  • it carries a little extra overhead and is less commonly needed. The other seven categories are on by default. Toggling a category takes effect on the next request, with no restart.

Persisting across requests ​

By default the viewer keeps the 25 most recent requests and drops older ones as new requests arrive, so you're looking at what just happened. Turn on Keep history (above the request list) to keep every request instead, which is handy when you're watching a sequence of requests and don't want earlier ones to disappear.

The viewer holds a bounded buffer of up to 2,000 events, so very old events are eventually evicted either way.

The Dumps window ​

The desktop app gives Dumps its own space:

  • The Dumps view lives in the main window (in the side navigation), where you pause and resume capture, open Setup for the per-category toggles, and browse captured requests.
  • A standalone Dumps window can be popped out so you can keep dumps visible next to your editor and browser while the rest of the app stays out of the way. It shows the same request list and detail, with Pause / Resume and pin on top in its title bar.

In either place you can filter a request's events by category and text, keep history, and clear the buffer.

How it works ​

When capture is enabled, Yerd's daemon runs a small TCP server bound to loopback (127.0.0.1) on a configurable port (default 2304). The yerd-dump extension - loaded into each PHP-FPM pool - opens a connection per request and streams one compact JSON frame per event. The daemon buffers those frames in memory and serves them to the desktop app.

Everything stays on your machine: the server binds loopback only, and if the port is already in use the daemon logs it and retries rather than failing - capture is never allowed to take your sites down.

No CLI commands

Dumps is driven entirely from the desktop app. There are no yerd CLI subcommands for it. Its settings are stored in your config file under a [dumps] table (enabled, port, persist, and per-feature toggles), which the app keeps in sync.

See also ​

A Forjed project. Released under the MIT License.