-
Notifications
You must be signed in to change notification settings - Fork 19
improve tracing coverage #131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
config/config.sample.pythtest.toml
Outdated
@@ -60,3 +60,12 @@ exporter.compute_unit_price_micro_lamports = 1000 | |||
# Note that this doesn't affect the rate at which transactions are published: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's hide it from sample files for the time being.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
im assuming you mean the opentelemetry config?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Can you also bump the version by minor?
This PR enhances tracing by introducing the
#[instrument]
macro to more functions and adding additional fields to the current span inget_product.rs
,subscribe_price.rs
, andsubscribe_price_sched.rs
. This approach is async safe as it maintains the reference to the current span without manual enter/exit, ensuring the tracing context is preserved across await points. We should avoid manual enter/exit tracing logs already handled by#[instrument]
, and any custom spans should be cautious of this behavior to avoid manual span entry.