Package-level declarations
Types
The distributed-trace context active on the current call.
Policy for the capture core: which events to keep and how to shape their attributes.
An out-of-band health signal for the log-capture edge.
A TraceContextProvider backed by the coroutine-context trace an app sets with withActiveTrace — the dependency-light, commonMain source for platforms with no ambient tracer (wasmJs, iOS, macOS).
The shared, platform-independent capture core.
A live log-capture installation — the LogCapture core plus the way to stop it.
A directly-settable TraceContextProvider — the escape hatch for apps or tests that cannot scope their tracing as coroutines (prefer withActiveTrace + CoroutineContextTraceProvider, which is the primary API).
A log event normalized to a platform-independent shape.
Supplies the trace context active on the current call, or null when none.
What to do with a log emitted outside any active trace.
Properties
The most events one drain turn hands to the exporter at once.
How deep the capture queue is — the buffer between the application's synchronous logging call and the drain coroutine that exports each event.
Attribute key under which a capture edge may record an exception's message.
Attribute key under which defaultAttributeMapper records the logger name.
Functions
The default CaptureConfig.attributeMapper: records the logger name under LOGGER_NAME_ATTRIBUTE, then the event's own attributes (which therefore win on key collision).
Install log capture — the single uniform entry point on every platform.
Run block with trace as the active trace for the log lines it emits, then restore the previously-active trace. The whole point of native trace context: whoever starts a span wraps the work, and kuilt's sampling gate then stamps or drops those lines by that trace — on wasmJs, iOS and macOS, not only the JVM.