Crates.io | metriken-core |
lib.rs | metriken-core |
version | |
source | src |
created_at | 2024-01-17 23:36:56.758869 |
updated_at | 2024-12-12 19:23:26.462721 |
description | A fast and lightweight metrics library |
homepage | https://github.com/pelikan-io/rustcommon |
repository | https://github.com/pelikan-io/rustcommon |
max_upload_size | |
id | 1103511 |
Cargo.toml error: | TOML parse error at line 22, column 1 | 22 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
Easily registered distributed metrics.
metriken
allows you to easily declare static metrics throughout your codebase.
Then, when you want to expose those metrics, you can access them all in one
place.
use metriken::{metric, Counter, Gauge, Value};
/// A counter metric named "<crate name>::COUNTER"
#[metric]
static COUNTER: Counter = Counter::new();
/// A gauge metric named "my.metric"
#[metric(name = "my.metric")]
static GAUGE: Gauge = Gauge::new();
fn main() {
COUNTER.increment();
for metric in &metriken::metrics() {
let name = metric.name();
match metric.value() {
Some(Value::Counter(val)) => println!("{name}: {val}"),
Some(Value::Gauge(val)) => println!("{name}: {val}"),
_ => println!("{name}: <custom>")
}
}
}
Code updating the metrics can always access them without needing to go through
any indirections. (It just means accessing a static!). Using linkme
, the
metrics are all gathered into a single global array that can then be used to
read all of them and expose them.