Skip to content

Commit

Permalink
Remove internal language-specific requirements from the batch span pr…
Browse files Browse the repository at this point in the history
…ocessor description. (#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.
  • Loading branch information
jkwatson authored and bogdandrutu committed Jan 24, 2020
1 parent 586b03f commit a4ce6fc
Showing 1 changed file with 9 additions and 12 deletions.
21 changes: 9 additions & 12 deletions specification/sdk-tracing.md
Original file line number Diff line number Diff line change
Expand Up @@ -233,28 +233,25 @@ Export all ended spans to the configured `Exporter` that have not yet been expor

#### Built-in span processors

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

##### Simple processor

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

**Configurable parameters:**

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

##### Batching processor

The implementation of the `SpanProcessor` that batches ended spans and pushes
them to the configured `SpanExporter`.

First the spans are added to a synchronized queue, then exported to the exporter
pipeline in batches. The implementation is responsible for managing the span
queue and sending batches of spans to the exporters. This processor can cause
high contention in a very high traffic service.
This is an implementation of the `SpanProcessor` which create batches of finished
spans and passes the export-friendly span data representations to the
configured `SpanExporter`.

**Configurable parameters:**

Expand Down

0 comments on commit a4ce6fc

Please sign in to comment.