Struct RemoteStatus 

#[non_exhaustive]
pub struct RemoteStatus {
    pub fetches: u64,
    pub last_fetch: Option<Instant>,
    pub last_fetch_duration: Option<Duration>,
    pub last_failure: Option<FailureStatus>,
    pub consecutive_failures: u32,
}

What is true of a remote source right now, for an operator asking.

The fetch half of the picture ConfigStatus starts, and deliberately the same picture rather than a second one: the same FailureStatus type, the same consecutive_failures meaning zero-is-healthy, the same recorded-where-it-happens rule, and the same rendering through telemetry::Exposition. Two vocabularies for one question is how two surfaces come to disagree after the first bug.

The two do not overlap, and the split is worth stating because it is the distinction an operator is actually asking about:

Question	Where it is answered
did the store answer	here
did the document install	ConfigStatus

A fetch that returned an unchanged document is a success here and is not an install there, which is exactly the case neither surface could report before this type existed.

What it does not carry

No document, no key, and no description of the store. A store’s description is its URL, and a store URL routinely embeds user:password@host — so nothing here is derived from describe, and the name a metric is labelled with is the caller’s own, exactly as it is for a ConfigStatus.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

fetches: u64

Documents this slot has received since the process started, whether pulled by refresh or pushed through RemoteSink::apply.

last_fetch: Option<Instant>

When the last of them arrived. None before the first.

last_fetch_duration: Option<Duration>

How long the last pulled fetch took.

None before the first pull, and None again after a document arrives by push: a watch loop’s own round trip is timed by the store crate that made it, and reporting the previous pull’s duration beside a push’s timestamp would be a number that is not about the fetch it appears to describe.

last_failure: Option<FailureStatus>

The most recent fetch that returned nothing, if there has been one. Kept after a later success: it is history, and consecutive_failures is the health.

consecutive_failures: u32

Fetches that returned nothing since one returned a document. Zero means healthy.

Implementations

impl RemoteStatus

pub fn reachable(&self) -> Option<bool>

Whether the store answered the last time it was asked.

Three states rather than two, and the third is the point: None before anything has been asked of the store at all. A source that has been installed and never fetched is not down — reporting it as down is how a scrape at startup pages somebody — so the metric is absent rather than zero, exactly as last_success_seconds is.

pub fn stale_for(&self) -> Option<Duration>

How long ago the last document arrived from the store.

None before the first. Monotonic, for the reason ConfigStatus::stale_for is: a wall clock going backwards under NTP would make a fresh fetch look stale.

Trait Implementations

impl Clone for RemoteStatus

fn clone(&self) -> RemoteStatus

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for RemoteStatus

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

Formats the value using the given formatter.

impl Default for RemoteStatus

fn default() -> RemoteStatus

Returns the “default value” for a type.

impl Eq for RemoteStatus

impl PartialEq for RemoteStatus

fn eq(&self, other: &RemoteStatus) -> bool

Equality operator ==.

fn ne(&self, other: &Rhs) -> bool

Inequality operator !=.

impl StructuralPartialEq for RemoteStatus