Follow a traceparent from browser telemetry to container logs.

Use this route in Azure Container Apps to produce paired client and server log events with a fresh W3C trace context per action.

Trace propagation

traceparent per action

Server render

2026-10-02T03:58:26.661Z

Request headers

traceparent
X-Correlation-ID

API endpoint

POST /api/observability/events

Traced flow

Browser signal, server processing, one trace

The browser writes a local console event, posts allowlisted telemetry to the server, and the server emits paired container log events with the same W3C trace context.

Last traced flow

No event emitted yet

BFF API trace

Next facade to BFF API

This calls a diagnostic API through the Next facade so the same correlation id follows a realistic downstream BFF request.

Last BFF API call

No event emitted yet

API event

API-handled event

This asks the generic observability endpoint to validate a bounded event and write it through the shared server logger with fresh trace and correlation headers.

Last API event

No event emitted yet

Client error

Controlled browser failure

This throws and catches a browser error, logs it locally, then relays a bounded error payload to the server under the same headers.

Last client error

No event emitted yet

Server error

Controlled runtime failure

This asks the API route to throw, catch, and log a controlled server error with the propagated trace and correlation headers.

Last server error

No event emitted yet