0.5.0-beta readiness tracker

[MikeGoldsmith]

This is a tracking issue for the requirements outlined in the beta release document: https://docs.google.com/document/d/1eviggoIguOS89dgKL-8ntUOCfPP6FLWAoQkGoBDsld0/edit#

Traces

• OpenTelemetry SpanWrapper on top of .NET Activity.
• Stable API of every spec'd feature Add TracerProvider #573
• SDK Implementation of every spec'd feature
• Move SamplerResult to SDK #574
• Sampler implementations missing XML comments #575
• Replace TracerFactory with TracerProvider #576
• Add ForceFlush() to SpanProcessor #577
• BatchingSpanProcessor missing exporterTimeout #578
• Basic tracing
• Named tracers
• Tracers use OTEP 66 Context mechanism - This is an implementation detail and does not affect the API

Metrics

• Documentation
• Examples
• Stable API of every spec'd feature
• SDK Implementation of every spec'd feature - No spec exists, so we have own spec.
• Basic SDK
• Add observer Combined Metrics API updates for v0.3 (Add Observer instrument, remove Gauge instrument, etc.) opentelemetry-specification#430
• Remove gauge Combined Metrics API updates for v0.3 (Add Observer instrument, remove Gauge instrument, etc.) opentelemetry-specification#430

Resources

• Stable API of every spec'd feature
• SDK Implementation of every spec'd feature

Context Propagation

• Stable API of every spec'd feature
• Basic context mechanism
• Global Propagators API Add Global Propagators API #581
• Global Context API (get and set active context) Separate Context propagation (OTEP-66) #461
• SDK Implementation of every spec'd feature
• Composite Propagator Composite Propagator #582
• Basic context mechanism

Exporters

• OpenTelemetry Native - Collector Exporter
• Prometheus
• Jaeger
• Zipkin

Instrumentation

• HTTP
• SQL

Docs and examples

• Instrumenting using Activity API or Span Wrapper for
• Exporting telemetry
• Configuring pipeline
• Adding instrumentation (aka adapters or auto-collectors)

[hacst]

@MikeGoldsmith Any updates on this or ETA for the beta? The general beta announcement post said "The .Net API + SDK will follow shortly." but it is really hard to get a feeling for how close this actually is as an outsider. Thanks.

[MikeGoldsmith]

Hi @hacst

I'll be updating this today / over the weekend ready for our next SIG call on Tuesday. With this complete, we should have a better picture of what is left for us to complete before we can release our first Beta release.

[giuliano-barberi-tf]

@MikeGoldsmith @SergeyKanzhelev I'm wondering if there's been any updates to the beta readiness. As an outsider I've also read a few blog posts about using OpenTelemetry in .NET but in this repo I couldn't find whether the beta is close or not. It's been a few months since the last update I'm wondering if anything has changed. Thanks!

[cijothomas]

@giuliano-barberi-tf We are currently focused on .NET Activity API integration with OpenTelemetry. We understand a lot of people are waiting for beta to arrive - I'd tentatively say June end based on this #684

I'll put on an agenda on next weeks SIG meeting, to discuss more on beta release, and update back here.

[czs1993]

The beta is completed? the readliness haven’t update for a long time. Thanks!

[cijothomas]

The beta is completed? the readliness haven’t update for a long time. Thanks!

No. This repo has never released a beta. We expect to have discussion on this tomorrow's SIG meeting.

[czs1993]

@cijothomas thanks, looking forward to the repo update.

[cijothomas]

Updated: As discussed, beta date is postponed from July 17 to July 24, so as to have DiagnosticSourcepreview7 available on Nuget. (OT packages depends on this package)

[cijothomas]

Since we are now able to track items using milestones, we no longer need this. closing. Let us know if this is still needed.
To know whats coming in next beta, this should help: https://github.com/open-telemetry/opentelemetry-dotnet/milestone/8