Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aligns exporting pipeline with SDK spec #227

Merged
merged 4 commits into from
Sep 23, 2019

Conversation

lmolkova
Copy link

@lmolkova lmolkova commented Sep 23, 2019

According to spec, Tracer should have processor(s): simple and batching.

Each processor has exporter which can export batch and shutdown

this change aligns implementation with spec (partially) and removes extra abstractions left from census.

Depends on #221, #222

Fixes #120, #223, #225

More to do: #224 (batching processor), #226 (multi-processor registration)

@lmolkova lmolkova changed the title Aligns exporting pipeline with SDK Aligns exporting pipeline with SDK spec Sep 23, 2019
@lmolkova lmolkova marked this pull request as ready for review September 23, 2019 16:04
{
this.worker.RegisterHandler(name, handler);
/// <summary>
/// Batch is successfully exported.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why batch is in the name of an enum in the abstract exporter?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

exporters always export list of spans. Batch vs non-batch exists only in processor.

{
protected readonly SpanExporter Exporter;

protected SpanProcessor(SpanExporter exporter)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can processors be chained?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tracer will have multiple processors, they are executed sequentially (not chained) per spec.

We'll handle processor registration in #226

// limitations under the License.
// </copyright>

namespace OpenTelemetry.Trace.Export.Test
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you for adding a test

Copy link
Member

@SergeyKanzhelev SergeyKanzhelev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just couple of comments. Looks good otherwise

@lmolkova lmolkova merged commit 762b5ce into open-telemetry:master Sep 23, 2019
Yun-Ting pushed a commit to Yun-Ting/opentelemetry-dotnet that referenced this pull request Oct 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Move exporter API and IStartEndHandler to SDK package
2 participants