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
Hi, thanks in advance.
Is it expected behaviour that json event formatter will produce double metadata for events emitted by log crate ?
In example below it has "target" field and "log.target" and there is no option to remove "log." metadata.
Locally defined JsonVisitor is not used. but it has feature part which should remove already recorded metadata from log crate.
But it is under fn record_debug and it seems that those log metadata will go to fn record_str
#[cfg(feature = "tracing-log")]
name if name.starts_with("log.") => (),
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, thanks in advance.
Is it expected behaviour that json event formatter will produce double metadata for events emitted by log crate ?
In example below it has "target" field and "log.target" and there is no option to remove "log." metadata.
Here is some notes I've found:
In tracing-subscriber Json even formatter
in this part of code where event fields are recorded and serialized:
Locally defined
JsonVisitor
is not used. but it has feature part which should remove already recorded metadata from log crate.But it is under
fn record_debug
and it seems that those log metadata will go tofn record_str
Beta Was this translation helpful? Give feedback.
All reactions