Module watch 

Watchlist runs (#47)

The I/O side of scope::watch: fetch reads each target’s metrics through the compute functions the CLI commands use (never a printing handler), and run repeats the ticks on the watchlist’s schedule with the one repeat runner, writes the CSV trail and the report.

The TUI’s monitor wizard and grid drive these functions.

Re-exports

pub use fetch::TargetReading;

pub use fetch::Tick;

pub use fetch::tick;

pub use run::csv_header;

pub use run::csv_rows;

pub use run::report_text;

pub use run::run;

Modules

fetch

One tick: read every target’s metrics and judge its rules.

monitor

scope monitor <args> as a watchlist: the arguments fill the monitor wizard (#47, design section 5.3).

run

A watchlist run: ticks on the watchlist’s schedule, through the one repeat runner, with the CSV trail and the final report.

Structs

Ready

A watchlist ready to run.

Sources

What the fetchers read with.

Functions

prepare

Makes the watchlist ready to run, once before the first tick: @label targets become their address and chain, and a token symbol that token metrics read is resolved to its contract. A symbol on many chains asks the user (in the TUI, as a list); the answer holds for the run.

venue_ids

The venue IDs a watchlist may name: the built-in and the user’s.