Struct State 

pub struct State {
    since: Option<i64>,
    firing: Option<i64>,
    value: f64,
    matched: usize,
    total: Option<usize>,
    error: Option<String>,
    at: i64,
}

What one rule is currently doing. Reported verbatim by /api/v1/alerts.

Fields

since: Option<i64>

When the comparison first held, in wall nanoseconds. Cleared the moment it stops holding, which is what makes hold a sustained breach rather than a count of breaching evaluations.

firing: Option<i64>

value: f64

matched: usize

total: Option<usize>

error: Option<String>

The last evaluation’s failure, if it failed. A rule whose query is unanswerable is not a quiet rule.

at: i64

Implementations

impl State

fn advance(&mut self, breaching: bool, now: i64, hold: i64) -> Option<bool>

Advance the state machine one evaluation, and say whether that is a notification: Some(true) fired, Some(false) resolved, None nothing changed.

A method rather than a match inside Engine::tick because the only interesting thing in this file has a clock in it, and a test that drives the clock has to drive this — a test carrying its own copy of these arms would pass while the engine did something else, which is how the last round of bugs in this repository survived its unit tests.

fn phase(&self) -> &'static str

Trait Implementations

impl Clone for State

fn clone(&self) -> State

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Default for State

fn default() -> State

Returns the “default value” for a type.