server tracing

[MFJoyBoy]

how can i enable server tracing?
is there any built-in way or configuration for handling server logs?

[gbj]

Leptos has built-in support for the tracing crate, which you can enable using the tracing and trace-component-props features.

Otherwise, you can set up and use tracing as you would for any other Rust application. There's no additional Leptos-specific configuration here.

[MFJoyBoy]

i set:
leptos = { version = "0.8.10", features = ["tracing", "trace-component-props"] }
when i run:
cargo leptos serve
i won't see any trace on terminal
am i missing something?

[MFJoyBoy]

this is the output i get:

    Finished `dev` profile [unoptimized + debuginfo] target(s) in 2m 03s
       Cargo finished cargo build --package=app --bin=app --no-default-features --features=ssr
     Serving at http://127.0.0.1:3000
listening on http://127.0.0.1:3000

[gbj]

I may have been unclear, or it might be that you're not familiar with how tracing works. tracing has two halves: libraries (like leptos) or your application can emit tracing events, either through the tracing attribute macro or through tracing::info!() etc. Adding the tracing features causes leptos, the library, to be instrumented with those macros.

Emitting tracing events does not do anything on its own. To capture those events you set up a tracing subscriber, which can handle them however you want: by logging them, sending them to a telemetry service, whatever.

You need to find a tracing subscriber that makes sense for you and set that up. You can consult the tracing docs for more information on any of this. Like I said, it is not leptos specific at all.

[MFJoyBoy]

i call thin function in ssr main:
#[cfg(feature = "ssr")]

fn setup_tracing() {
    use tracing_subscriber::{layer::SubscriberExt, util::SubscriberInitExt};

    tracing_subscriber::registry()
        .with(
            tracing_subscriber::EnvFilter::try_from_default_env()
                .unwrap_or_else(|_| format!("api=trace,tower_http=trace,utilities=trace,controllers=trace").into()),
        )
        .with(tracing_subscriber::fmt::layer())
        .init();
}

[MFJoyBoy]

ops i forgot to update filter :)

[MFJoyBoy]

how about server binary logs? could it be configured with binary itself or it should be configured with the system manager like systemd itself
by binary itself i mean like configuration in cargo.toml, or environment variables
so when server binary run, it create directory and files for writing logs

[gbj]

You control main.rs and the server environment — you can write whatever code you want in it, to do that. It is not related to the framework.