OpenTelemetry context in structured events

Test the integration

Send and verify events with OpenTelemetry context in structured events

Use OpenTelemetry context in structured events where your app knows the final result. Collect only the fields you need, then verify a test event before building charts.

1
Choose the outcome
Trace-to-event correlation
2
Define the contract
trace_id and span_id from the active span
3
Log the final result
This pattern enriches a Telemetry event with OpenTelemetry context; it does not send OTLP data to Telemetry.
4
Check the stored event
Exercise a known fixture, then inspect checkout_completed for one correctly typed terminal row.

Before you start

An existing OpenTelemetry SDK and context propagation setup
The telemetry-sh package initialized server-side
A defined business event that complements span-level diagnostics

Delivery setup

Install and initialize server-side

Import telemetry-sh in server-only code and initialize it once with process.env.TELEMETRY_API_KEY. Keep ingestion credentials out of browser bundles, client-visible environment variables, source control, logs, and exception messages.

opentelemetry-install

npm installation

bash

npm install telemetry-sh

1Create one reusable server-side client. Set its timeout and retry limit.
2Log an event when the operation succeeds, fails, retries, or times out.
3Send test events with known results and inspect the stored rows before enabling an alert.

Snippet

Start with one structured event

Add this shape where the workflow completes, fails, or retries. Then build the dashboard from real fields.

opentelemetry

OpenTelemetry context in structured events event

javascript

import { trace } from "@opentelemetry/api";

const spanContext = trace.getActiveSpan()?.spanContext();

await telemetry.log("checkout_completed", {
  status: "success",
  latency_ms: 684,
  trace_id: spanContext?.traceId,
  span_id: spanContext?.spanId,
  checkout_version: "v2",
  account_id: account.id,
});

Event schema

trace_id and span_id from the active span

workflow name, status, duration, and error category

Safe account, release, or feature dimensions

Check your setup

Checkpoint 1

This pattern enriches a Telemetry event with OpenTelemetry context; it does not send OTLP data to Telemetry.

Checkpoint 2

Emit the business outcome once, while spans retain dependency-level timing.

Checkpoint 3

Treat trace and span IDs as correlation fields for lookup, not chart dimensions.

Verification

Prove the event arrived

Run this after exercising known success and failure cases. Replace the fallback table name if your final event contract differs from the snippet.

opentelemetry-verification

OpenTelemetry context in structured events verification query

sql

SELECT *
FROM checkout_completed
ORDER BY timestamp_utc DESC
LIMIT 20;

Confirm one terminal row per logical outcome, with the expected status, identifiers, units, and UTC time.

Inspect the inferred schema and verify that retries do not change field types or generate a new logical event ID.

Search the stored fields for credentials, raw payloads, prompts, private content, and unbounded error messages.

Exercise a provider timeout, ingestion rejection, and process shutdown before treating the dashboard as complete.

Implementation references

Review the event contract, data-safety guidance, and upstream primary documentation before enabling a new production path.

Logs, metrics, traces, and events Correlation IDs OpenTelemetry JavaScript

Where to log

Keep the outcome event small and recoverable

This pattern provides

Record the outcome as an event you can query with SQL.
Stable fields for dashboards, alerts, and cross-event correlation.
Test events for checking success, failure, retries, and timeouts.

This pattern does not provide

An OTLP exporter, automatic collection pipeline, or replacement for detailed traces and diagnostic logs.
Exactly-once delivery merely because the payload contains an event ID.
Permission to collect raw provider payloads, user content, credentials, or regulated data.

Delivery and idempotency Batching and shutdown Troubleshoot ingestion

Example event schemas

Check what each event records, when to send it, and which field types it needs. Review the example payload and privacy checklist before using it in production.

API reliability10 fields