Being able to rename field `message` key

[barakadax]

Feature Request

Motivation

Changing key message to msg

Proposal

There are more than 1 value we get in tracing & tracing-subscriber but some places work with Pascal, some camel and some snake cases, the option to edit also default fields like message key would be appreciated

[rissson]

FWIW we've been using #23 on top of 0.2.7 without any particular issue

[barakadax]

If you can provide me with a snippet of how to use both packages and rename any field of my choosing feel free to close this issue

[rissson]

We use my fork with the changes from #23 applied on top of the latest 0.2.7 release:

json-subscriber = { git = "https://github.com/rissson/json-subscriber.git", rev = "950ad7cb887a0a14fd5cb8afb8e76db1f456c032" }

And then we do:

let mut json_layer = json_subscriber::fmt::layer()
    .with_file(true)
    .with_line_number(true)
    .flatten_event(true)
    .flatten_current_span_on_top_level(true);

let inner_layer = json_layer.inner_layer_mut();
inner_layer.with_thread_ids("thread_id");
inner_layer.with_thread_names("thread_name");
inner_layer.with_flattened_event_with_renames(
    move |name, map| match map.get(name) {
        Some(name) => name.as_str(),
        None => name,
    },
    HashMap::from([("message".to_owned(), "event".to_owned())]),
);

I don't think this issue should be closed until #23 is accepted, but that's up to the maintainer

[mladedav]

Yeah, sorry, I had to do some other stuff and forgot about the PR. I remember I wanted something more general, but I'm glad it works for you.

I'll probably just merge that the for now, it's taking too long to keep arguing that "one day I might build better solution".

[rissson]

thank you very much!