pub struct LagReport {
pub gate_us: u64,
pub observed_ops: u64,
pub decision_p50_us: Option<u64>,
pub decision_p99_us: Option<u64>,
pub decision_max_us: u64,
pub decision_breaches: u64,
pub durable_p50_us: Option<u64>,
pub durable_p99_us: Option<u64>,
pub durable_max_us: u64,
pub durable_breaches: u64,
pub pending_breaches: usize,
}Expand description
What the meter has seen since the process started.
Percentiles are bucket upper bounds capped at the observed maximum, so they over-estimate by at most a factor of two and never under-estimate.
Fields§
§gate_us: u64The gate these counts are measured against, microseconds.
observed_ops: u64Accepted ops measured. Rejections are not ops and are not counted.
decision_p50_us: Option<u64>Median dequeue -> append: the gate as literally written.
decision_p99_us: Option<u64>99th percentile dequeue -> append.
decision_max_us: u64Slowest dequeue -> append observed.
decision_breaches: u64Accepted ops whose append alone reached the gate.
durable_p50_us: Option<u64>Median dequeue -> acknowledgement, durability barrier included: what a submitter waits out.
durable_p99_us: Option<u64>99th percentile dequeue -> acknowledgement.
durable_max_us: u64Slowest dequeue -> acknowledgement observed.
durable_breaches: u64Accepted ops that reached the gate through the barrier. This is the breach count the lag log records.
pending_breaches: usizeBreaches recorded but not yet drained to the operator’s lag log.