Use Recorder’s reproduction and request identifiers to connect browser evidence with backend logs and traces. This requires a connected recording and application middleware or other instrumentation that logs the incoming headers.

Recorder identifiers

The minimal set of identifiers produced by RECORDER:

• x-fairlead-reproduction-id identifies the recording attempt and is sent during connected capture.
• x-fairlead-issue-id identifies the selected issue when enabled and supplied.
• x-fairlead-correlation-id identifies an individual request when enabled.

Account-free recordings do not send these headers. Capture domain rules do not limit header injection; requests to third-party origins can receive the identifiers too.

Inspect the supplied network.har for request headers and use Correlate with backend logs for verification. Locally recorded IDs alone do not establish that a server received them. If the required header is missing, ask the tester for the identifier or a newly reviewed artifact.

Format boundaries

The runtime Report and downloadable artifacts are described in Report structure and artifact formats. It does not establish a shared header contract for other Fairlead products.