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 we can only rely on the output from the log crate for debugging. When there are multiple components that dump into the log, it is not easy to understand what thread does what.
The tracing crate provides structural output. It also can be easily integrated with the OpenTelemetry framework.
The text was updated successfully, but these errors were encountered:
The log crate also seems to support structural logging with kv feature enabled per its document. Not sure how easy that is to integrate with OpenTelemetry yet.
The opentelemetry-rust project states logs are alpha, but it seems that logs have a good chance to be integrated depending on the current logging library in use.
For the traces, indeed the opentelemetry-rust project recommends using the tracing crate on their readme. Actually it seems strange, as the OpenTelemetry framework could be used directly. But one could also wrap both somehow and chose at the compile time, if needed.
It seems it need some exercise also to ensure the solution plays ok with OpenTelemetry.
At the moment we can only rely on the output from the
log
crate for debugging. When there are multiple components that dump into the log, it is not easy to understand what thread does what.The
tracing
crate provides structural output. It also can be easily integrated with the OpenTelemetry framework.The text was updated successfully, but these errors were encountered: