Lalit Kumar Bhasin
Lalit Kumar Bhasin
> > @owent do you think the below dependence on grpc++ can be marked as public? Which may fix the issue as well? > > https://github.com/open-telemetry/opentelemetry-cpp/blob/2544803a37d527acdc0f8b7af4b720336e7c14bc/exporters/otlp/CMakeLists.txt#L38-L39 > > No, in...
Moving to post GA, as it doesn't affect public facing API.
> We use "trace", "logs", "metrics". Proposing to make it consistent and rename "trace" to "traces". The namespaces are `opentelemetry::trace`, `opentelemetry_sdk::trace` in implementation, so `trace` actually makes sense from that...
@ankitkapur - Do you have plan to work on this, or can we close it based on reasoning given in above comments ?
Yeah we can close it I guess. We have user docs in opentelemetry.io. API docs can remain in readthedocs as of now. Unless @marcalff has some other thoughts.
As discussed in last community meeting, this seems to be scenario where caller having a background thread running as the globals are being torn down. These background threads are still...
> Hello @lalitb, Do you have any plan or timeline to add synchronous gauge support for OpenTelemetry SDK C++? Sorry, no timeline yet. It may take a couple of months...
"@KallDrexx, nit - do you think including the `no-attribute scenario` text in the title would provide more clarity on what this PR is targeting?
@ramgdev Thanks for volunteering to add the support. This looks to be in the right direction, and good to review once ready.
> Were you able to test this impl against some of the single level hashmap alternative implementations? @hdost Do you have any alternative implemetations in mind, can test that. I...