Skip to content

Add Raven Dashboard: CPU, memory and Winners history - #2514

Merged
sr320 merged 1 commit into
masterfrom
raven-dashboard
Oct 3, 2026
Merged

sr320 merged 1 commit into
masterfrom
raven-dashboard

Conversation

@sr320

@sr320 sr320 commented Oct 3, 2026

Copy link
Copy Markdown
Member

New Raven Dashboard page (next to Gannet Dashboard in the nav), built from raven's daily ghr.log snapshot.

Data

  • fetch_raven_stats now also parses memory_percent, the Winners list (top 5 accounts by summed %CPU, with %MEM), and the top memory processes.
  • Raven overwrites ghr.log daily with no dated copies, so check_servers.py --out now maintains status/raven_history.json on the server-status branch: one entry per snapshot date (CPU, memory, per-mount %, Winners), capped at 365 days. publish_status.sh already checks out the branch first, so the file carries forward. History starts from the first run after merge.

Page (docs/Raven-Dashboard.md, docs/javascripts/raven-dashboard.js)

  • Tiles: CPU, memory, fullest drive, top (non-system) user.
  • Line chart of CPU % and memory % by day (shared chart from gannet-health.js).
  • Winners: latest table, plus a user × day grid of appearances, shaded by CPU, with a day count per user. System accounts (root, mysql, rstudio+…) are listed last in gray.
  • Current top-memory processes and drive table.
  • Computing Hardware links to it from the raven row and the Raven Disk / CPU section.

Tested the parser against the live ghr.log and rendered the page locally with 21 days of synthetic history.

🤖 Generated with Claude Code

check_servers.py now parses raven's memory line, Winners list and top
memory processes, and accumulates a daily raven_history.json on the
server-status branch (raven keeps no dated copies of ghr.log). A new
Raven Dashboard page charts CPU and memory over time and shows a
per-user grid of appearances in the Winners list.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sr320
sr320 merged commit 1789850 into master Oct 3, 2026
2 checks 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.

1 participant