fleet run -history -state-key first writes the last 30 days into obs-beacond's database, from the same plan and clock the live demo runs on: hosts' hours (load now a function of name and clock: working day per site time zone, weekends, memory creep, disks filling until clean-up; part of #40), cluster workloads, array I/O, IBM i CPU, Vault leases, mail rounds, statuses for the reports, and an incident for each past spell with notes on the stories. About 45 s for the full demo. Docs: demo.md, development.md.
The demo container needs the new flags in its entrypoint (hosts-baseline), which goes with the next demo deploy.
fleet run -history <database> -state-key <file> first writes the last 30 days into obs-beacond's database, from the same plan and clock the live demo runs on: hosts' hours (load now a function of name and clock: working day per site time zone, weekends, memory creep, disks filling until clean-up; part of #40), cluster workloads, array I/O, IBM i CPU, Vault leases, mail rounds, statuses for the reports, and an incident for each past spell with notes on the stories. About 45 s for the full demo. Docs: demo.md, development.md.
The demo container needs the new flags in its entrypoint (hosts-baseline), which goes with the next demo deploy.
Closes #39.
Every graph on the demo said "none kept yet" and the reports had
nothing to report: the container starts fresh each week. Now fleet run
-history <database> -state-key <file> first writes the last 30 days into
obs-beacond's database, from the same plan and clock the live demo runs
on:
- hosts' hours: what a host uses is now a function of its name and the
clock (load.go): a working day in its site's time zone, quieter
weekends, memory that creeps on some hosts until a weekly restart, and
disks at a level of their own that fill slowly until a clean-up
(fleet-0023's log volume warns now and then). No more every disk at
33%, part of #40;
- the clusters' workloads, the arrays' I/O and space, the IBM i
partitions' CPU, the Vaults' leases (on a daily curve now), the mail
rounds;
- hosts', checks' and services' statuses, for the reports' availability;
- an incident each time a past problem came and went (pastProblems in
scenario.go, with obs-beacond's keys and titles), notes on the stories
saying what the cause was, and the incident numbers carrying on.
About 45 seconds for the full demo. state gains PutHostHours,
PutMailRounds and LogStatuses, to write many in one transaction.
docs/demo.md and docs/development.md describe it.
Closes#39.
A month of every workload was 1.6 million rows and 280 MB, more than the
demo container's 256 MB tmpfs. The clusters themselves and their nodes,
the arrays, partitions and Vaults keep their 30 days; the thousands of
controllers and VMs get the last 7. 86 MB, written in 13 seconds.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
fleet run -history -state-key first writes the last 30 days into obs-beacond's database, from the same plan and clock the live demo runs on: hosts' hours (load now a function of name and clock: working day per site time zone, weekends, memory creep, disks filling until clean-up; part of #40), cluster workloads, array I/O, IBM i CPU, Vault leases, mail rounds, statuses for the reports, and an incident for each past spell with notes on the stories. About 45 s for the full demo. Docs: demo.md, development.md.
The demo container needs the new flags in its entrypoint (hosts-baseline), which goes with the next demo deploy.
Closes #39.