feat(derive): Move to tracing
for telemetry
#94
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Note
RFC on if we want to keep our own telemetry utils.
Moves to the
tracing
crate for telemetry, rather than the hand-rolled solution. Thetracing
crate provides simple macros and a robust collection system for traces, which can be leveraged in testing and in live environments. Because consumers of this crate, likemagi
andreth
, usetracing
, these telemetry logs will also be captured by their trace subscirbers.In addition, trace collection can be avoided by not having a global subscriber, leaving no impact on performance in the case of the telemetry logs not being used. This will be advantageous for performance in the
client
program, where we want to avoid superfluous heap allocation.