OpenTelemetry - CNCF/opentelemetry-cpp: Release v1.0.0

Name: opentelemetry-cpp

Owner: OpenTelemetry - CNCF

Release: opentelemetry v1.0.0

Released: 2021-09-20

License: Apache-2.0

Release Assets:

v1.0.0 release

Release of core packages:

  • opentelemetry-api
  • opentelemetry-sdk

and exporter packages:

  • opentelemetry-exporter-otlp ( gRPC + HTTP/JSON )
  • opentelemetry-exporter-etw
  • opentelemetry-exporter-zipkin
  • opentelemetry-exporter-jaeger ( thrift + UDP/HTTP )

Changelog

API

  • Document DefaultSpan, remove DefaultTracer (#959)
  • Separate baggage<->Context api from Baggage Propagator (#963)
  • Remove unused public API to_span_ptr (#964)
  • 💥 Make span context management public (#967)
  • Support determining parent span from Context while creating new Span (#969)
  • 💥 Traces: Add note on experimental semantic convention implementation, prefix semantics headers with experimental tag (#970)
  • Increment OPENTELEMETRY_ABI_VERSION_NO to 1 (#980)

SDK

  • Clean up GetEnvironmentVariable and remove unused variable under NO_GETENV (#976)
  • 💥 Resources: Add note on experimental semantic convention implementation, prefix semantics headers with experimental tag (#970)

OTLP Exporter

  • 🐛 Ignore status description if status code is not Error (#962)
  • 💥 Make Otlp exporter configuration environment variables specs-compliant (#974)

Zipkin Exporter

  • 🐛 Don't set parentId in case parentId is empty (#943)
  • 🚀 Extend zipkin exporter with ability to provide headers (#951)

DOCS

  • :book: Add getting-started documentation for SDK: (#942)
  • :book: Remove unnecessary spaces and spelling of gRPC in README (#965)

BUILD

  • Disable bazel build for gcc 4.8, upgrade versions for grpc(v1.39.1) and bazel(4.2.0), document bazel support (#953)
  • Move CMake config template to cmake folder (#958)
  • Enable CMake to search the new package variable <PackageName>_ROOT (#975)
  • 🐛 Do not override CMAKE_CXX_STANDARD (#977)

🚧 Experiemental Features (Will change in future)

  • Semantic Conventions for traces - As the specs is still experimental, the implementation will change in future.
  • Semantic Convention for resource - As the specs is still experimental, the implementation will change in future.
  • Logs and Metrics API & SDK - These are not compliant, and are behind feature flag. Not recommended to use for now.

To top