OpenTelemetry Certified Associate (OTCA) free question 4 / 10 · Domain 2: The OpenTelemetry API and SDK
How does the simple span processor hand spans to the exporter?
- It passes finished spans to the exporter as soon as they end, serializing the Export calls
- It collects spans in a queue and exports them when the scheduled delay elapses
- It exports the spans that the sampler marked as errors, and keeps the rest in memory
- It exports spans in parallel, so that a slow exporter does not delay the application
Show the answer and explanation
Answer: A
Why this is correct
The simple processor "passes finished spans and passes the export-friendly span data representation to the configured SpanExporter, as soon as they are finished." It must synchronize calls to the exporter's Export so they are not invoked concurrently. Its only configurable parameter is the exporter, in contrast to the batching processor with its queue and delay settings.
Why the other options are wrong
"It collects spans in a queue and exports them when the scheduled delay elapses" … Queueing with a scheduled delay describes the batching processor.
"It exports spans in parallel, so that a slow exporter does not delay the application" … The processor must synchronize calls to Export so that they are not invoked concurrently.
"It exports the spans that the sampler marked as errors, and keeps the rest in memory" … Which spans exist is a sampler decision. The processor forwards finished spans to the configured exporter.
Key points
Simple processor: immediate and serialized, useful for debugging. Batching processor: queued and efficient, the usual choice for production.