OpenTelemetry Distributed Tracing

End-to-end request correlation across asynchronous messaging architectures using W3C TraceContext standards and OpenTelemetry instrumentation.

Observability Capability (REQ-111): EventOre inspects, extracts, propagates, and visualizes W3C traceparent headers across all supported brokers, enabling instantaneous jump-to-trace navigation in Jaeger, Zipkin, Datadog, and Dynatrace.

The Challenge of Asynchronous Tracing

In HTTP REST microservices, distributed tracing propagates cleanly via headers. In asynchronous message architectures (Kafka, RabbitMQ, MQTT, Kinesis), producers and consumers are decoupled in time and space.

When an incident occurs — such as an order dropping or processing latency spiking — identifying the upstream root cause across multiple topics and queues can require hours of manual log parsing. EventOre bridges this gap by automatically detecting and decoding distributed trace contexts in every record.

W3C TraceContext Specification

EventOre natively parses the official W3C traceparent binary or string header:

version - trace_id                         - parent_id        - trace_flags
00      - 4bf92f3577b34da6a3ce929d0e0e4736 - 00f067aa0ba902b7 - 01

When EventOre's message inspector or live stream intercepts a record containing traceparent (or legacy X-B3-TraceId), it highlights the Trace ID with a direct clickable icon that opens your centralized observability platform.

Bridge Span Propagation

When using EventOre's Replication Bridge Engine, EventOre acts as an active distributed tracing participant:

Configuring Observability Links

Configure your organization's APM base URL in application.yml or environment variables:

eventore:
  tracing:
    enabled: true
    apm-provider: jaeger # Options: jaeger, zipkin, datadog, custom
    apm-url-template: "https://jaeger.internal.corp/trace/{traceId}"
    # Example for Datadog:
    # apm-url-template: "https://app.datadoghq.com/apm/trace/{traceId}"
    inject-bridge-spans: true

UI Tracing Features