Skip to content

Commit b225ec0

Browse files
jkwatsonSergey Kanzhelev
authored andcommitted
Remove internal language-specific requirements from the batch span processor description. (open-telemetry#417)
* Remove internal language-specific requirements from the batch span processor description. Also, clean up the language slightly. * Add the "unmodified" clarification * add a clarification about the format of the data being pushed to an exporter.
1 parent e3c9507 commit b225ec0

1 file changed

Lines changed: 9 additions & 12 deletions

File tree

specification/sdk-tracing.md

Lines changed: 9 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -233,28 +233,25 @@ Export all ended spans to the configured `Exporter` that have not yet been expor
233233

234234
#### Built-in span processors
235235

236-
SDK MUST implement simple and batch processors described below. Other common
237-
processing scenarios should be first considered for implementation out-of-process
238-
in [OpenTelemetry Collector](overview.md#collector)
236+
The standard OpenTelemetry SDK MUST implement both simple and batch processors,
237+
as described below. Other common processing scenarios should be first considered
238+
for implementation out-of-process in [OpenTelemetry Collector](overview.md#collector)
239239

240240
##### Simple processor
241241

242-
The implementation of `SpanProcessor` that passes ended span directly to the
243-
configured `SpanExporter`.
242+
This is an implementation of `SpanProcessor` which passes finished spans
243+
and passes the export-friendly span data representation to the configured
244+
`SpanExporter`, as soon as they are finished.
244245

245246
**Configurable parameters:**
246247

247248
* `exporter` - the exporter where the spans are pushed.
248249

249250
##### Batching processor
250251

251-
The implementation of the `SpanProcessor` that batches ended spans and pushes
252-
them to the configured `SpanExporter`.
253-
254-
First the spans are added to a synchronized queue, then exported to the exporter
255-
pipeline in batches. The implementation is responsible for managing the span
256-
queue and sending batches of spans to the exporters. This processor can cause
257-
high contention in a very high traffic service.
252+
This is an implementation of the `SpanProcessor` which create batches of finished
253+
spans and passes the export-friendly span data representations to the
254+
configured `SpanExporter`.
258255

259256
**Configurable parameters:**
260257

0 commit comments

Comments
 (0)