Tracking hyper-based services

[ristillu]

I'm messing around with a proof of concept using hyper, axum, tokio et al. I thought I'd try your console and it's great. One additional thing I'd like to have though is a little more control over some of the fields, such as the name column for starters. Given I'm not manually spawning threads, I'm using basis axum router + handlers, is there any way with the console stack and/or tracing to manually set these? I don't want to contrive up wrapper tasks just for this functionality? I mean, I can contrive handlers for axum endpoints that I can see are being hit in the console but if I build up this POC I'd like to know which of many are being hit at any time.

Things I've tried:

#[tracing::instrument(some_attributes)]  // tried name, target, fields, can't get any annotated in the console.
#[track_caller]  // hoping this might opaquely annotate "something".
tracing::info!(target: "some_name", "some message");  // before I started reading, when I was hoping the span might be annotated ...

Hopefully you understand what I'm asking, otherwise I can probably throw together some minimal reproducible POC over the weekend.

[ristillu]

Just a bit of further information today. The way it is I have for example one of my Axum/hyper routed callbacks being invoked and all I get in my console are a list of tokio::task targets and the location for every one is <cargo>/hyper-0.14.18/src/common/exec.rs:49:21 and the Fields are all kind=task. That totally makes sense to me.

If I rejig one of the callback handlers to be something like:

fn handler() {
    tokio::task::Builder::new()
        .name("foobar".into())
        .spawn(async move {
            // do stuff
        }).await;
}

Then I get the behaviour I want but it's really contrived, it requires tokio_unstable (of course so does the console currently), my linters in my neovim/LSP environment complain and I complicate things just for the sake of the name that I want. But the console looks the way I want it to.

[ristillu]

After doing a bunch more reading I see that naming tasks in the way I want is a relatively active topic of discussion in the tokio community and I probably need to be more patient.