IncomingEntryBuilder

Redact the values of the given keys throughout the data.

Final storage pass for entry payloads. Earlier builders redact known request surfaces, but this keeps persisted entries private if a future collector path adds sensitive data before save.

Redact the values of the given lowercase keys at every depth.

Flatten the given headers, redacting the sensitive ones and the sensitive query parameters of URL headers.

Normalize the configured sensitive keys to unique lowercase strings.

Redact sensitive query parameters from the URLs in the data.

Redact the values of sensitive query parameters. A parameter matches when its decoded name or any of its bracketed segments (e.g. filter[secret]) is a sensitive key. The query is not parsed and rebuilt, so every other byte of the URL is kept as recorded, and relative or malformed URLs are redacted the same way.

Replace leaf values that cannot be stored as JSON with a marker.

Determine if the value can be stored as JSON.

Create a new incoming entry builder instance.

Build the entry for the given request and response.

Merge the collector payload recorded while rendering into the entry.

Redact the recorded prop values.

Nested props are recorded under their dotted path, so a value is redacted when any segment of its path is a sensitive key.

Get the given payload value when it is a string.

Get the given payload value when it is an array.

Get the normalized route from the collector payload.

Get the normalized render source from the collector payload.

Resolve the kind of request the entry records.

A non-Inertia request that rendered an Inertia page (component present in the collector payload) is the app's initial page load. One that rendered no Inertia page is a plain HTTP request the app serves alongside Inertia.

Resolve the location the response redirects to.

Capture the request body.

Capture the response body.

Capture the page object of an Inertia response.

Cast the page object to the JSON the client received. Resolved props still hold live values here (a model, a date, the always-shared errors object), and the storage pass would replace those object leaves with a marker.

Capture the body of a non-Inertia response (plain JSON/text endpoints the app serves alongside Inertia). Binary, streamed, and oversized bodies are omitted.

Determine if the content type is textual.

Capture the given body value when it can be encoded.

Confirm a value survives JSON encoding with the flags the repository persists it with. An un-encodable value would otherwise throw at save and drop the entry.

Replace individual leaf values that cannot be JSON encoded with a marker, keeping the surrounding structure intact. Prop values are shared verbatim by the app, so a single non-UTF-8 attribute must not fail the whole entry at save.

Capture the given body string when it is valid UTF-8.

Replace uploaded files with a lightweight summary so binary contents are never serialized into an entry.

Summarize the given uploaded file.

Resolve the render source for route-defined renders (Route::inertia), which have no user-space render call site. The definition location is captured onto the route defaults by the Route::inertia() macro when the route is registered.

Determine if the route carries no information.

Get the normalized route from the request.

Get the milliseconds elapsed since the request started.

Get the keys whose values are redacted.