You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was playing with tracing and OpenTelemetry and I was noticing that under some conditions, my test applications were not sending traces at all.
Looking at one of the examples, I saw opentelemetry::global::shutdown_tracer_provider(). Adding this at the end of my program made things work reliably (apparently!).
I think this is related to very short programs that run quickly. Somehow accumulated traces are lost on exit.
Proposal
While this is documented in the opentelemetry crate, and I found it in the examples, I think users of this crate would appreciate some nudging towards this.
Alternatives
Or perhaps, the shutdown can happen automatically? That would be even better.
The text was updated successfully, but these errors were encountered:
Feature Request
Motivation
I was playing with tracing and OpenTelemetry and I was noticing that under some conditions, my test applications were not sending traces at all.
Looking at one of the examples, I saw
opentelemetry::global::shutdown_tracer_provider()
. Adding this at the end of my program made things work reliably (apparently!).I think this is related to very short programs that run quickly. Somehow accumulated traces are lost on exit.
Proposal
While this is documented in the
opentelemetry
crate, and I found it in the examples, I think users of this crate would appreciate some nudging towards this.Alternatives
Or perhaps, the shutdown can happen automatically? That would be even better.
The text was updated successfully, but these errors were encountered: