Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Commit

Permalink
Update target docs
Browse files Browse the repository at this point in the history
  • Loading branch information
mrcnski committed May 25, 2023
1 parent 71388e6 commit 6f3aa53
Showing 1 changed file with 8 additions and 5 deletions.
13 changes: 8 additions & 5 deletions node/gum/src/lib.rs
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@
//!
//! ### Log levels
//!
//! All of the the [`tracing` macros](https://docs.rs/tracing/latest/tracing/index.html#macros) log level macros are available.
//! All of the the [`tracing` macros](https://docs.rs/tracing/latest/tracing/index.html#macros) are available.
//! In decreasing order of priority they are:
//!
//! - `error!`
Expand All @@ -54,11 +54,14 @@
//! The `LOG_TARGET` should be defined once per crate, e.g.:
//!
//! ```rs
//! const LOG_TARGET: &str = "parachain::pvf::prepare-worker";
//! const LOG_TARGET: &str = "parachain::pvf";
//! ```
//!
//! The target can be an arbitrary string, but we use the `::` syntax to mimic
//! Rust's module separators.
//! This should be of the form `<target>::<subtarget>`, where the `::<subtarget>` is optional.
//!
//! The target and subtarget are used when debugging by specializing the Grafana Loki query to
//! filter specific subsystem logs. The more specific the query is the better when approaching the
//! query response limit.
//!
//! ### Fields
//!
Expand Down Expand Up @@ -99,7 +102,7 @@
//! ```
//!
//! On the other hand if you want all `parachain` logs, specify `parachain=trace`, which will also
//! include logs from `parachain::pvf` and other sub-modules.
//! include logs from `parachain::pvf` and other subtargets.

pub use tracing::{enabled, event, Level};

Expand Down

0 comments on commit 6f3aa53

Please sign in to comment.