Beta Readiness Tracker

[dyladan]

Due date: March 16th, 2020

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

Initialization

• Simplify initialization Simplify initialization #823

Documentation and Examples

• Setting up exporters for Prometheus and Jaeger.
• Creating a manual “hello world” client / server app with completely manual instrumentation. Includes Docker containers for Prometheus and Jaeger and explains how to start them.
• Adding OpenTelemetry to an existing HTTP client / server application that uses an instrumented framework.
• Setting up the Collector
• Semantic conventions for creating exporters. For example, how to convert from OpenTelemetry span semantics to Jaeger.
• Generic documentation that introduces readers to traces, spans, metrics, context propagation

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 feat: use context-based tracing #816

Metrics

• stable API of every spec'd feature
• SDK Implementation of every spec'd feature
  • Basic SDK feat: Metrics SDK - aggregator, batcher, controller #738 Implement Metrics SDK #402
  • Add observer Combined Metrics API updates for v0.3 (Add Observer instrument, remove Gauge instrument, etc.) opentelemetry-specification#430 [spec] Remove gauge, add observer #739
  • Remove gauge Combined Metrics API updates for v0.3 (Add Observer instrument, remove Gauge instrument, etc.) opentelemetry-specification#430
  • push controller
    • pull controller Create a PullController for metrics #796 (stretch goal)

Resources

• underlying package created
• SDK Implementation of every spec'd feature Add Resource API #789 Resources API: package, semantic conventions, and test utils #815
  • Add resource to tracer/meter provider Add resource to TracerProvider and MeterProvider #840
    • Resource auto detection Resource auto-detection #841 (stretch goal)
  • Export resource with spans to collector export resource to exporters #843
  • Add resource to spans in other exporters export resource to exporters #843

Context Propagation

• stable API of every spec'd feature Separate layer for context propagation #741
  • Basic context mechanism Separate context propagation (OTEP 66) #769
  • Global Propagators API Update propagators API for OTEP 66 #777 Add propagation API #797
  • Global Context API (get and set active context) Add context API #792
  • Correlation Context API Rename DistributedContext to CorrelationContext #834
    • Correlation Context propagator feat: implement W3C Correlation Context propagator #838 (stretch goal)
• SDK Implementation of every spec'd feature
  • Basic context mechanism Separate context propagation (OTEP 66) #769
  • Global Propagators Update propagators API for OTEP 66 #777
  • Composite Propagator feat: add composite propagator #821
  • Propagator Getter/Setter Argument Add getter and setter arguments to propagation API #827

Exporters

• OpenTelemetry Native - Collector Exporter
  • gRPC support Send data to opentelemetry-collector using grpc for node only #567 (stretch goal)
• Prometheus
• Jaeger
• Zipkin (stretch goal)

Integrations

• HTTP
• gRPC
• SQL
• At least one popular framework
  • express feat: add express plugin #666 #685 Automatic tracing of express #666
• Automatic testing of integrations (stretch goal)

Examples

• manual tracing hello world example
• http client/server using an instrumented framework
• gRPC client/server

[dyladan]

@mtwo It was mentioned in gitter that Baggage seems to have been left off of your google doc. Was that intentional, or is it considered part of the tracing API?

[mtwo]

@bogdandrutu, @carlosalberto, or @SergeyKanzhelev can answer

[dyladan]

added resources @mayurkale22 it has been added to the beta release plan

[mayurkale22]

@dyladan Can we close this one now?