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
we've run into issues using add_fields in different API contexts because we want to be able to set high level request context for logs deep in the call stack (vs passing down values or setting up convoluted error catching). we've added a forked_log middleware to our axum http router and our grpc service. is there any tooling or practices for protecting against using add_fields too many times outside of a forked telemetry logger?
The text was updated successfully, but these errors were encountered:
we've run into issues using
add_fields
in different API contexts because we want to be able to set high level request context for logs deep in the call stack (vs passing down values or setting up convoluted error catching). we've added aforked_log
middleware to our axum http router and our grpc service. is there any tooling or practices for protecting against usingadd_fields
too many times outside of a forked telemetry logger?The text was updated successfully, but these errors were encountered: