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?
we've run into issues using
add_fieldsin 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_logmiddleware to our axum http router and our grpc service. is there any tooling or practices for protecting against usingadd_fieldstoo many times outside of a forked telemetry logger?