Beta Readiness Tracker

[codeboten]

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

Traces

• stable API of every spec'd feature
• SDK Implementation of every spec'd feature
  • Basic tracing
  • Named tracers
  • Tracers use OTEP 66 Context mechanism - This is an implementation detail and does not affect the API Implement the Propagation API #415

Metrics

• stable API of every spec'd feature
  • Observer API Implement observer instrument #425
  • Named meters and config Implement "named" meters + Remove "Batcher" from Meter constructor #431
• SDK Implementation of every spec'd feature
  • Basic SDK
  • All metrics SDK issues: Implement Metrics SDK #414

Resources

• stable API of every spec'd feature
• SDK Implementation of every spec'd feature Implement Resources SDK #456

Context Propagation

• stable API of every spec'd feature
  • Basic context mechanism Adding Context API #395
  • Global Propagators API Implement the Propagation API #415
  • Global Context API (get and set active context) Adding Context API #395
  • Correlation Context API Implement Correlations API #416
• SDK Implementation of every spec'd feature
  • Basic context mechanism Adding Context API #395
  • Global Propagators Implement the Propagation API #415

Exporters

• OpenTelemetry Native - Collector Exporter Add OT collector trace exporter #343 Add OT collector metrics exporter #344
• Prometheus Add Prometheus exporter #157
• Jaeger
• Zipkin (stretch goal)

Integrations

• HTTP
• gRPC Add gRPC integration #276
• SQL
• At least one popular framework
  • flask
• Automatic testing of integrations (stretch goal)

Examples

• manual tracing hello world example
• http client/server using an instrumented framework
• gRPC client/server Add gRPC integration #276

[Oberon00]

There is one important and rather basic thing that's missing here: https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/sdk-resource.md

[codeboten]

That's a good point, I didn't see anything in the JS beta tracker, or in the OpenTelemetry Launch Plan about resources. Do you have anymore info on this @mtwo?

[mtwo]

Resource metadata is required; @bogdandrutu or @carlosalberto can confirm. I've updated the launch plan doc to reflect this.

@dyladan can you update the JS beta tracker to reflect this?

[codeboten]

Section for resources was added.

[toumorokoshi]

After a discussion with @jmacd in gitter, I've clarified that the resource SDK today calls for 1. an implementation of resources and 2. a way to bind them into the Tracers that are created.

We have 1 already:

• https://github.com/open-telemetry/opentelemetry-python/blob/master/opentelemetry-sdk/src/opentelemetry/sdk/resources/__init__.py
• https://github.com/open-telemetry/opentelemetry-python/blob/master/opentelemetry-api/src/opentelemetry/resources/__init__.py

We do not yet have 2: https://github.com/open-telemetry/opentelemetry-python/blob/master/opentelemetry-sdk/src/opentelemetry/sdk/trace/__init__.py#L573

As it's still ambiguous what Resources will eventually be used for, and an OTEP around Resources in a broader term, Unless someone with more context can inform, we probably just need to be able to a handle to a Resource object to the traceprovider: open-telemetry/oteps#78

[codeboten]

@mtwo is the OpenTracing bridge still part of the beta requirement? It doesn't appear in the launch doc.

[mtwo]

It's not a requirement for beta, though I think that a few languages will be including it anyways. I assume that we'll have it as a RC / GA requirement, though we haven't set these yet.

[c24t]

Moving the gRPC integration and examples forward to the next milestone and closing this one out.