Module telemetry

Optional execution spans and application log correlation.

Applications own providers, exporters, sampling and shutdown. Enabling this feature installs none of those components. Propagation requires the exact advertised capability and existing original claim gates. A configured PHP Server can advertise support. Missing, malformed or unknown capabilities use independent task traces. A Server version alone does not enable propagation. Attempt spans are children of their task.

See the setup example for the optional Cargo feature, application-owned provider/exporter and W3C propagator configuration. Native Server and Cloud adoption require separate qualification, as described in the runtime support matrix.

Modules

carrier

Bounded portable observations, never task/receipt/lease authority.

Structs

ExecutionLogRecord

Application log record whose execution IDs are resolved when it is emitted. Buffering attributes permits replacing stale durable IDs without duplicate keys; application attributes such as request_id keep their original value.

ExecutionLogger

Logger returned by ExecutionLoggerProvider.

ExecutionLoggerProvider

Decorate the application’s OpenTelemetry logger provider with execution IDs. Use this provider in an OpenTelemetry log or tracing bridge. Its lifecycle remains owned by the application; ordinary log bodies and request IDs remain application-owned. No logging bridge is installed automatically.

ExecutionTelemetry

Opt-in worker telemetry using an application-owned tracer.

Functions

current_log_context

Bounded execution identifiers. Values contain no arguments, results, headers, exception messages or baggage. Trace IDs reflect the current application span, including an application-created HTTP/database child span.