#metrics #open-telemetry #atomic #observable #sync #obs #updated

influxive-otel-atomic-obs

Opentelemetry observable metric implementations based on std::sync::atomic types

7 releases

0.0.3-alpha.1 Jun 5, 2024
0.0.2-alpha.1 Oct 16, 2023
0.0.1-alpha.11 Aug 4, 2023
0.0.1-alpha.9 Jul 31, 2023

#478 in Development tools

Download history 382/week @ 2024-03-25 459/week @ 2024-04-01 691/week @ 2024-04-08 698/week @ 2024-04-15 787/week @ 2024-04-22 780/week @ 2024-04-29 650/week @ 2024-05-06 554/week @ 2024-05-13 763/week @ 2024-05-20 779/week @ 2024-05-27 1050/week @ 2024-06-03 701/week @ 2024-06-10 697/week @ 2024-06-17 709/week @ 2024-06-24 435/week @ 2024-07-01 644/week @ 2024-07-08

2,513 downloads per month
Used in 17 crates (2 directly)

MIT/Apache

26KB
594 lines

Opentelemetry observable metric implementations based on std::sync::atomic types. Opentelemetry has a concept of "observable" metrics that are not reported as they are updated, but rather, when an update happens, they are polled. For ease-of-use in code, it is often desirable to have these metrics be backed by std::sync::atomic types, so that they can be easily updated throughout the code, and fetched whenever a metric reporting poll occurs. This crate provides the [MeterExt] trait and associated types to make it easy to use std::sync::atomic backed metrics with opentelemetry.

Example

use influxive_otel_atomic_obs::MeterExt;

let (my_metric, _) = opentelemetry_api::global::meter("my_meter")
    .u64_observable_gauge_atomic("my_metric", 0)
    .init();

my_metric.set(66); // probably will not be reported
my_metric.set(99); // probably will not be reported
my_metric.set(42); // will be reported next time reporting runs

Dependencies

~2.1–3MB
~56K SLoC