Trace / Correlation ID Extractor
Scan pasted text or logs and extract likely trace, request, and correlation identifiers.
What is Trace / Correlation ID Extractor?
Find common trace, request and correlation identifiers in copied log text. A matching string is a navigation aid; it does not establish parent/child spans or prove that two failures share one cause.
How to use Trace / Correlation ID Extractor?
Step 1
Paste log text, headers, or free-form debugging notes.
Step 2
Run extraction to identify likely unique IDs.
Step 3
Review the deduplicated results and copy the ones you need.
Example input / output
A log excerpt containing requestId=demo-42 can be matched with an HTTP response's X-Request-ID. Keep timestamps and service names alongside the identifier in the incident note.
Example input
requestId=4f5d1e2a-3b44-4d65-9872-0ff13c1fa221 traceparent=00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-00 correlationId=01H8XW1ST0G43A3K8T2VSPT8SBCheck the result
- Custom internal ID formats may not match the built-in patterns.
- Very short identifiers can be filtered out intentionally to reduce false positives.
Practical developer examples
Check identifier scope
Some IDs belong to a single request, others to an entire workflow. Confirm where your gateway and services create and forward them.
Handle naming differences
trace_id, traceId and traceparent are different formats. Verify extracted values against the original line rather than treating every token as a standard trace ID.
Common developer use cases
Only recognized textual patterns are extracted. Missing results can indicate another logging format, not absence of tracing.
Common issues
FAQ
Can this reconstruct a distributed trace?
No. Use an observability backend for span relationships, timings and sampling context.
Can I share an extracted ID?
Review its sensitivity and surrounding metadata first; IDs can identify internal operations.