$rangedloop.SequenceObserver
rangedloop.SequenceObserver is two different things depending on how you look at it: a generic scheduling wrapper in the rangedloop package, and — in practice, in the satellite — the durability report.
It counts, per segment, how many pieces sit on usable nodes — online, not suspended, not exiting — minus the k needed to rebuild. Then it recounts after deleting the biggest group (subnet, wallet, operator), showing how much of your durability rests on a single point of failure.
- Claude
Though at the moment I’ve not figure out how to structurally format to read the report, this is a cheap attempt to show you what this can do.
Anyhow, should this observer be called durability.Observer instead?
Minimum command
./satellite-modular ranged-loop-once \
--components='$rangedloop.SequenceObserver' \
--durability.classes=last_net \ # last_net,last_ip,wallet,email
--eventkit.destination=otel \
--otel.logging.stdout=pretty \
--otel.logging.print-eventkit=true \
--identity-dir=id/satellite \
--metainfo.database-url="postgres://my_role:123456@127.0.0.1:26257/my_metainfo_database?sslmode=verify-full&sslrootcert=ca.crt" \
--database-options.url="postgres://my_role:123456@127.0.0.1:26257/my_database?sslmode=verify-full&sslrootcert=ca.crt"
These three flags: --eventkit.destination=otel, --otel.logging.stdout=pretty and --otel.logging.print-eventkit=true are for displaying the result to stdout so you have a vague idea what kind of data you are dealing with.
#TODO: figure out the framework to read/query these data, keywords: class, healthy_pieces, count, missing_providers, placement, exemplars, retrievable_pieces..