Logs and traces for a Kotlin coroutine service: the current span is a CoroutineContext element, an event is a @Serializable type, and export is a background drain

MongoDB exporter for stx-telemetry: a batch is one insertMany, and retention is a TTL index rather than a job

OTLP/HTTP export for stx-telemetry, in JSON over the JDK's own HttpClient — kotlinx.serialization and no OpenTelemetry SDK

The SLF4J bridge for stx-telemetry, in both directions: third-party logs into the pipeline, or this library's signals out to an existing logback

Ktor plugin for stx-telemetry: one telemetry per application, and a server span per request that continues the incoming traceparent

Spring Boot auto-configuration for stx-telemetry, opt-in behind stx.telemetry, with a CoWebFilter that makes each request a server span