-
Notifications
You must be signed in to change notification settings - Fork 18
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
Port opentelemetry code to multichain codebase #428
Comments
We now have our node logs in gcp, for example: multichain-dev-1 |
The logging functionality works, but it is spammed with |
Seems the SEVERITY level only applies to log from GCP side, not logs from multichain service. I'm working with Kody on this |
Looks like we can port severity level by using this library to set up the global logging subscriber: https://github.com/NAlexPear/tracing-stackdriver |
Is it compatible with our current tracing APIs? If not, I would not invest time in it now. Feel free to move it back to backlog if it's time-consuming. |
not entirely sure. I'll move it back to backlog for now. |
Mostly involves porting the tracing-opentelemetry gluecode from the old codebase: https://github.com/near/mpc-recovery/blob/develop/mpc-recovery/src/logging.rs
We also used to have tracing endpoints, but not sure if that's relevant anymore as we are not exposing any user-facing API anymore: https://github.com/near/mpc-recovery/blob/develop/mpc-recovery/src/leader_node/mod.rs#L119-L122
The text was updated successfully, but these errors were encountered: