TRACE-ID

Trace ID. The unique observability identifier that an EDI message preserves across every system it traverses.

Definition

A Trace ID is a unique identifier assigned to a message upon entry into the system and propagated unchanged through every stage it traverses: reception, mapping, validation, archiving, emission. It enables correlating in milliseconds every event tied to a single message in a centralised observability system (ELK, Datadog, Splunk, OpenTelemetry). It complements the functional identifier (AS2 Message-ID, Interchange Control Number) by adding a cross-cutting dimension.

Origin

The Trace ID concept stems from the distributed-observability domain, formalised by the W3C Trace Context standard (2020) after emerging at Google (Dapper, 2010), Twitter (Zipkin, 2012) and Uber (Jaeger, 2017). Its adoption in the EDI world dates from the 2020s with the spread of OpenTelemetry and cloud-native architectures. Today, modern B2B gateways (Boomi, MuleSoft, B2B/EDI Management) emit a Trace ID per message, often in W3C trace-id format (32 hex characters).

Example in context

traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01

Every event tied to a message carries this W3C trace-context header in logs and spans: reception at the AP, decryption, Schematron validation, mapping, archiving, acknowledgement emission, backend ERP transmission. A query "trace_id:4bf92f3577b34da6a3ce929d0e0e4736" in the observability system returns the full trace in milliseconds.

Related terms

• Audit trail — journal that gets enriched with the Trace ID.
• Idempotency — operational property where Trace ID plays a key role.
• MDN — acknowledgement that can carry the Trace ID in a custom header.