-
Notifications
You must be signed in to change notification settings - Fork 8
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
NDEV-2175: Use tracing::instrument and request id on neon-api endpoints #188
Conversation
6ef0eca
to
edbca43
Compare
edbca43
to
4a2155a
Compare
Can we not print out account data, when the field data is too big? |
@Deniskore I checked our logs and found some like this:
Both
There are also some logs like:
where data field can become very large and |
1265088
to
cc570fd
Compare
cc570fd
to
342a061
Compare
…ts (#188) * NDEV-2175: Use tracing::instrument on neon-api endpoints * Add request id * cargo clippy * Custom Debug implementation for TxParamsRequestModel
…ts (#188) * NDEV-2175: Use tracing::instrument on neon-api endpoints * Add request id * cargo clippy * Custom Debug implementation for TxParamsRequestModel
…ts (#188) * NDEV-2175: Use tracing::instrument on neon-api endpoints * Add request id * cargo clippy * Custom Debug implementation for TxParamsRequestModel
…ts (#188) * NDEV-2175: Use tracing::instrument on neon-api endpoints * Add request id * cargo clippy * Custom Debug implementation for TxParamsRequestModel
Used
tracing::instrument
onneon-api
endpoints to help with correlating logs.As an example, logs for this request:
http://localhost:8080/api/get-ether-account-data?ether=0xbf7043bf6f60ada5b71b0ef7a0264baf93edd1cc&slot=240249818
before this PR:become:
Each request has an unique ID present on each log span of that request.