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
At the moment, enabling debugging via OTEL_OCAML_DEBUG=true ./binary.exe only prints information like the following:
opentelemetry: send http POST to http://127.0.0.1:5996/v1/traces (963B)
opentelemetry: send http POST to http://127.0.0.1:5996/v1/traces (963B)
I'd like, additionally, the ability to print on every single span entered and exited — effectively a verbose mode.
Is this better attached to OTEL_OCAML_DEBUG=true, implemented as a new payload like OTEL_OCAML_DEBUG=verbose, or as a separate env-var, like OTEL_OCAML_VERBOSE=true?
The text was updated successfully, but these errors were encountered:
At the moment, enabling debugging via
OTEL_OCAML_DEBUG=true ./binary.exe
only prints information like the following:I'd like, additionally, the ability to print on every single span entered and exited — effectively a verbose mode.
Is this better attached to
OTEL_OCAML_DEBUG=true
, implemented as a new payload likeOTEL_OCAML_DEBUG=verbose
, or as a separate env-var, likeOTEL_OCAML_VERBOSE=true
?The text was updated successfully, but these errors were encountered: