Use Fairlead identifiers to find backend logs for a recorded request. This requires a connected project and an application that accepts and logs the headers. Account-free recording does not send them.

Distinguish the identifiers

Header	Identifies
x-fairlead-issue-id	The selected issue, when enabled and supplied
x-fairlead-reproduction-id	The recording attempt
x-fairlead-correlation-id	An individual request, when enabled

A reproduction can contain many requests with different correlation identifiers. Do not use one per-request ID as the identifier for the entire test run.

Configure the application

Connected recordings send the reproduction ID with intercepted requests. Issue and per-request correlation IDs depend on their settings. Capture domain rules do not restrict header injection: requests from the recorded tab to third-party origins can also receive these identifiers. Review the application’s external requests before recording.

Have your project administrator configure the optional identifiers. Configure backend middleware to retain the incoming identifiers in request logs and, where appropriate, propagate diagnostic context to downstream services.

Check proxies and cross-origin configuration so the intended headers are accepted and preserved. Validate with a safe test request; do not assume a configured header reached the server merely because an identifier exists in the report.

Find the matching logs

1. Open network.har from the supplied bundle in a HAR viewer or editor.
2. Find the relevant request and inspect its Fairlead identifiers and available request headers.
3. Search backend logs for the exact per-request correlation ID or reproduction ID.
4. Compare request URL, timestamps, environment, and response details.

If the required header was removed, redacted, or not included in the handoff, ask for the identifier or a newly reviewed artifact.

Account-free recording does not send these headers to the application backend. Locally recorded identifiers alone cannot locate server logs that never received them.

Use existing trace headers

Project trace mappings can extract trace identifiers from configured request or response headers. Match the mapping to the application’s actual tracing convention and use the extracted value with your existing observability tools.

A mapping records correlation evidence; it does not automatically configure middleware or provide a complete distributed trace.

Diagnose missing matches

Check the selected project, identifier settings, and whether a proxy removed the header. Confirm the correct environment and log retention period, then inspect server logging itself.

If the application never logged the identifier, use the available URL and timing context and state the weaker association. Recorder cannot retroactively create backend correlation.