Struct opentelemetry_tide::MetricsConfig

pub struct MetricsConfig {
    pub global_labels: Option<Vec<KeyValue>>,
    pub boundaries: Vec<f64>,
    pub quantiles: Vec<f64>,
    pub route: String,
}

Configuration for the metrics middleware

Unless you need specific values, MetricsConfig::default() should be fine for most use cases.

In your application you can shortcut that further down to Default::default(), so you don’t have to bring this struct into scope with a use.

Fields

global_labels: Option<Vec<KeyValue>>

Optional vec of key value pairs which then get added as labels to all metrics

boundaries: Vec<f64>

A vec of histogram boundaries; set your own fine-tuned buckets for your services

quantiles: Vec<f64>

A vec of summary quantiles (currently no prometheus-exportable metric is using them)

route: String

The route which will be used for metrics scraping by prometheus

Implementations

impl MetricsConfig

pub fn new(
    global_labels: Option<Vec<KeyValue>>,
    boundaries: Vec<f64>,
    quantiles: Vec<f64>,
    route: String
) -> Self

Initializes a MetricsConfig

Trait Implementations

impl Debug for MetricsConfig

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for MetricsConfig

fn default() -> Self

Returns the “default value” for a type.