Skip to content

Commit

Permalink
Clarify when to use simple vs. batching span processors
Browse files Browse the repository at this point in the history
  • Loading branch information
Rachel Klein committed Oct 15, 2020
1 parent 89d36ab commit e146850
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions specification/trace/sdk.md
Original file line number Diff line number Diff line change
Expand Up @@ -400,6 +400,11 @@ This is an implementation of `SpanProcessor` which passes finished spans
and the export-friendly span data representation to the configured
`SpanExporter` as soon as they are finished.

Typically, the simple processor will be most suitable for use in testing and/or
in scenarios where creating multiple threads is not desirable, since batching
span processors will typically be threaded in order to pass spans on to exporters
in the background.

**Configurable parameters:**

* `exporter` - the exporter where the spans are pushed.
Expand All @@ -410,6 +415,9 @@ This is an implementation of `SpanProcessor` which creates batches of finished
spans and passes the export-friendly span data representations to the
configured `SpanExporter`.

Typically, the batching processor will be more suitable for production environments
than the simple processor.

**Configurable parameters:**

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

0 comments on commit e146850

Please sign in to comment.