Skip to content

feat: mayfly stats - #38

Merged
Variiuz merged 1 commit into
mainfrom
feat/stats
Nov 10, 2026
Merged

Variiuz merged 1 commit into
mainfrom
feat/stats

Conversation

@Variiuz

@Variiuz Variiuz commented Nov 10, 2026

Copy link
Copy Markdown
Owner

mayfly status shows the moment; nothing showed how a slot did over a day. mayfly stats [hours] reads the slot journal (journalctl -u 'mayfly-slot@*', last 24 h by default) and prints per slot:

SLOT           GUESTS   JOBS   IDLE  STUCK    CUT ERRORS   MEDIAN
heavy-1             2      1      0      1      0      0   42 min
light-1             2      2      0      0      0      0    7 min
all                 4      3      0      1      0      0   15 min
  • GUESTS: guests destroyed; JOBS: those that ran a job (GUESTS minus IDLE and STUCK)
  • IDLE: replaced after MAX_IDLE_HOURS without a job; STUCK: runner never came online
  • CUT: jobs stopped by MAX_JOB_HOURS, the backstop or a full pool
  • ERRORS: clone, start, GitHub registration, a pod that never got ready
  • MEDIAN: life of a guest that ran a job; pods count VMs and errors only

It parses the lines bash and Rust slots already log, so it works for both engines and needs no new state. Help (both sides, parity 58/58) and README updated.

Tested: unit tests for the tally, cargo test/clippy, parity, tests/run.sh, and a run against a stub journalctl.

Notes: new mayfly stats [hours] shows per-slot jobs, idle and stuck guests and errors.


Generated by Claude Code

…rom the journal

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GGBbe8FgqqUCF5fNkd9Ndi
@Variiuz
Variiuz merged commit 338b1c7 into main Nov 10, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants