kora-telemetry-tracinglisted

# Kora Telemetry Tracing > **Kora sub-skill — obey the [kora-v1 meta rules](../../SKILL.md) on every task:** **R0** ensure `.kora-agent/` docs+examples are cloned · **R1** read this sub-skill before writing code · **R2** Kora APIs only — no Spring/Micronaut/Quarkus, no invented annotations or config keys · **R3** journal any incorrect Kora usage. Add comments/Javadoc only if asked. Kora collects traces in the OpenTelemetry standard and exports them in OTLP format. The framework already emits baseline spans for supported modules (HTTP server/client, database, Kafka, gRPC); you add an exporter module, point it at a collector, and optionally create manual spans for business steps the framework cannot infer. Read this when: - adding an OTLP exporter (`OpentelemetryGrpcExporterModule` or `OpentelemetryHttpExporterModule`), - configuring `tracing.exporter` toward Jaeger, Zipkin, or Grafana Tempo, - creating manual spans with the injected `Tracer` and correct parent context, - propagating `OpentelemetryContext` across async / coroutine boundaries, - overriding the default `Sampler`. ## Quick Start ### 1. Dependency The example repo pins the BOM via `kora-parent`; all Kora artifacts inherit that version, so never version a `ru.tinkoff.kora:*` artifact yourself. === "Java" ```groovy dependencies { koraBom platform("ru.tinkoff.kora:kora-parent:1.2.19") annotationProcessor "ru.tinkoff.kora:annotation-processors" // OTLP over gRPC (recommended)