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
Since we are using the OpenTracing library that is an archived project we might switch to OpenTelemetry as they also suggest on their main OpenTracing webpage.
From my understanding, there is support within bee to collect tracing spans and that this was used in early development in conjunction with Jaeger for assisting with diagnosing / debugging node interactions. This is one of the main reasons why there are "headers" within the libp2p setup within bee. Having this capability - but no demonstration / documentation on how to use it - represents tangible limitations on new client developers (and perhaps some present client developers).
The text was updated successfully, but these errors were encountered:
Location
N/A
Description
Originally posted by @martinconic in #5005
From my understanding, there is support within
bee
to collect tracing spans and that this was used in early development in conjunction with Jaeger for assisting with diagnosing / debugging node interactions. This is one of the main reasons why there are "headers" within thelibp2p
setup withinbee
. Having this capability - but no demonstration / documentation on how to use it - represents tangible limitations on new client developers (and perhaps some present client developers).The text was updated successfully, but these errors were encountered: