Skip to main content
Every iii function invocation receives a traceId (via new Logger()) that is automatically propagated to downstream queue handlers. All logs emitted through the context logger are structured JSON and correlated to the active trace.

Multi-step workflow with trace correlation

Step 2 — Queue processor

Step 3 — Notification

OpenTelemetry setup

The iii SDK exports traces and metrics automatically via the engine’s OpenTelemetry pipeline (OTLP over the WebSocket). No separate exporter configuration is required.

Logger methods

Key concepts

  • currentTraceId() / current_trace_id() is the W3C trace-context ID for the current invocation. It is automatically propagated to all downstream workers when you emit an event — no manual header passing is needed.
  • All logs are emitted as structured JSON via the engine’s log.info / log.warn / log.error functions.
  • The Node.js SDK supports OTel configuration directly in registerWorker(). Python and Rust use the engine’s built-in OTLP pipeline.
  • Log every step at entry and exit with the traceId to make multi-step flows fully observable.