opentelemetry-cpp
opentelemetry-cpp copied to clipboard
The OpenTelemetry C++ Client
Project tracking for SIG C++. Related: * https://github.com/open-telemetry/oteps/pull/212 * https://github.com/open-telemetry/opentelemetry-specification/issues/2731
Fixes #2506 ## Changes Please provide a brief description of the changes here. * Removed methods related to `Flush()` and `Close()` from the `API` class `opentelemetry::trace::Tracer`, starting with ABI version...
In the current OpenTelemetry ETW Log exporter, the attribute for table name is hard-coded to `"Log"` (see below 2 links for more details). The table name is useful for grouping...
*Describe your environment linux, gcc 7.3.1, protobuf 26.1, latest opentelemetry-cpp Steps to reproduce mkdir otel-cpp-starter cd otel-cpp-starter git clone https://github.com/open-telemetry/opentelemetry-cpp.git git submodule update --init cd opentelemetry-cpp mkdir build cd build...
**Is your feature request related to a problem?** GCP as platform use Cloud Trace. Currently most of service are able to consume correctly `WC3` propagation headers. Notable exception of this...
**Is your feature request related to a problem?** When I want to use OpenTelemetry C++ I currently have 2 options to do so: 1. I build the code myself from...
Fixes #2674 ## Changes + Use `fwrite`, `fflush` to keep it thread-safety. + Add `OPENTELEMETRY_ATTRIBUTE_LIFETIME_BOUND` , `OPENTELEMETRY_SANITIZER_NO_MEMORY` , `OPENTELEMETRY_SANITIZER_NO_THREAD`, `OPENTELEMETRY_SANITIZER_NO_ADDRESS`, `OPENTELEMETRY_HAVE_BUILTIN`, `OPENTELEMETRY_HAVE_FEATURE`, `OPENTELEMETRY_HAVE_ATTRIBUTE`, `OPENTELEMETRY_HAVE_CPP_ATTRIBUTE` For significant contributions please make sure...
This updates bazel as well as the deps that were required to be updated in order to support the newer version of bazel. Fixes https://github.com/open-telemetry/opentelemetry-cpp/issues/2619
Fixes #2676 ## Changes + Read default proto version from `third_party_release` + Format `cmake/opentelemetry-proto.cmake` For significant contributions please make sure you have completed the following items: * [ ] `CHANGELOG.md`...
In light of #2676 and #2677, it turns out upgrading each dependency is not trivial, because versions numbers for each dependencies are spread in multiple files in the source code,...