OpenTelemetry - CNCF/opentelemetry-cpp: Release v1.9.0
Name: opentelemetry-cpp
Owner: OpenTelemetry - CNCF
Release: OpenTelemetry C++ v1.9.0
Released: 2023-04-13
License: Apache-2.0
Release Assets:
v1.9.0 release
Release of core packages
- opentelemetry-api
- opentelemetry-sdk
and exporter packages:
- opentelemetry-exporter-otlp (gRPC + HTTP/JSON)
CI
- [CI] Make build environment parallel (Windows) #2080
- [CI] Make build environment parallel (Linux) #2076
- [CI] Remove separate run of metrics ostream example #2030
BUILD
- [BUILD] Include directory path added for Zipkin exporter example #2069
- [BUILD] Ignore more warning in generated protobuf files #2067
- [BUILD] Clean warnings in ETW exporters #2063
- [BUILD] Fix default value of OPENTELEMETRY_INSTALL_default #2062
SEMANTIC CONVENTIONS
- [SEMANTIC CONVENTIONS] Upgrade to version 1.20.0 #2088
- [SEMANTIC CONVENTIONS] Upgrade to version 1.19.0 #2017
API
- [API] Checking indices before dereference in string utils #2040
- [API] Export factory class of log provider #2041
SDK
- [SDK] Implement Forceflush for Periodic Metric Reader #2064
- [SDK] Add
ForceFlush
for allLogRecordExporter
andSpanExporter
#2000 - [SDK] Fix schema URL precedence bug in
Resource::Merge
#2036 - [SDK] Use sdk_start_ts for MetricData start_ts for instruments having cumulative aggregation temporality. #2086
EXPORTER
- [EXPORTER] Add OTLP HTTP SSL support #1793
- [EXPORTER] GRPC endpoint scheme should take precedence over OTEL_EXPORTER_OTLP_TRACES_INSECURE #2060
EXAMPLES
- [EXAMPLES] Remove unused 'alerting' section from prometheus.yml in examples #2055
- [EXAMPLES] Fix view names in Prometheus example #2034
DOC
- [DOC] Fix some docs typo #2057
- [DOC] Update OpenTracing shim README.md #2028
- [DOC] INSTALL doc clarifications #2078
Important changes:
- [EXPORTER] GRPC endpoint scheme should take precedence over OTEL_EXPORTER_OTLP_TRACES_INSECURE
#2060
- The logic to decide whether or not an OTLP GRPC exporter uses SSL has
changed to comply with the specification:
- Before this change, the following settings were evaluated, in order:
- OTEL_EXPORTER_OTLP_TRACES_INSECURE (starting with 1.8.3)
- OTEL_EXPORTER_OTLP_INSECURE (starting with 1.8.3)
- OTEL_EXPORTER_OTLP_TRACES_SSL_ENABLE
- OTEL_EXPORTER_OTLP_SSL_ENABLE
- With this change, the following settings are evaluated, in order:
- The GRPC endpoint scheme, if provided:
- "https" imply with SSL,
- "http" imply without ssl.
- OTEL_EXPORTER_OTLP_TRACES_INSECURE
- OTEL_EXPORTER_OTLP_INSECURE
- OTEL_EXPORTER_OTLP_TRACES_SSL_ENABLE
- OTEL_EXPORTER_OTLP_SSL_ENABLE
- The GRPC endpoint scheme, if provided:
- As a result, a behavior change for GRPC SSL is possible, because the endpoint scheme now takes precedence. Please verify configuration settings for the GRPC endpoint.
- Before this change, the following settings were evaluated, in order:
- The logic to decide whether or not an OTLP GRPC exporter uses SSL has
changed to comply with the specification:
- [SDK] Add
ForceFlush
for allLogRecordExporter
andSpanExporter
#2000LogRecordExporter
andSpanExporter
add a new virtual functionForceFlush
, and if users implement any customizedLogRecordExporter
andSpanExporter
, they should also implement this function. There should be no impact if users only use factory to create exporters.
New Contributors
- @chalin made their first contribution in https://github.com/open-telemetry/opentelemetry-cpp/pull/2028
- @Ziy1-Tan made their first contribution in https://github.com/open-telemetry/opentelemetry-cpp/pull/2057
- @cngzhnp made their first contribution in https://github.com/open-telemetry/opentelemetry-cpp/pull/2069
Deprecations
- The Jaeger Exporter is deprecated, see DEPRECATED for details.
Full Changelog: https://github.com/open-telemetry/opentelemetry-cpp/compare/v1.8.3...v1.9.0