Marc Alff

As discussed in community meeting, expanding the scope from "moving static variables to *.cc" to "moving all code to *.cc".

After investigations, it turns out there are 3 different ways to build with nlohmann_json in the top level CMakeList.txt. (1) CMake finds a nlohmann_json package. Message printed: `Using external nlohmann::json`...

Before changing makefiles for (3), I would like to understand if (3) is even needed at all. Downloading code manually from github sounds redundant with git submodules, which are already...

Also, picking an existing external nlohmann-json dependency might bring a different version, causing subtle bugs, especially considering the external package (1) takes precedence over git submodules (2)

Thanks @lalitb for the clarifications. Sorry I missed the existing issues.

Method Tracer::StartSpan() takes the following input: - a span name (1 combination) - attributes (K1 combinations) - links (K2 combinations) - options (K3 combination) so when exposing all variations in...

Please note that opentelemetry-cpp contains recent changes that have some impact on the C++ demo here. # SDK builders [TRACE SDK] Add trace sdk builders (#1393) https://github.com/open-telemetry/opentelemetry-cpp/pull/1471 This change provides...

Ok in principle, this will allows to disable telemetry in every applications the same way, without application specific options, or no options at all when the application forgot to provide...

> @marcalff see [this comment](https://github.com/open-telemetry/opentelemetry-specification/issues/2729#issuecomment-1222584006). The current thinking is that any boolean environment variable should be named `*_ENABLED_*` or `*_DISABLED_*` such that if a default value of false aligns with...

Greetings, When code can be loaded and unloaded in a dynamic plugin (for example, dlopen() in C/C++), the application needs a way to unregister asynchronous instruments on unload, to avoid...