Add complete map analytics pipeline to answer: "Which maps drive the most players? Is my rotation working?" Backend Changes: - Migration 005: Add map_id FK to server_stats and wipe_history tables - Stats consumer now captures current_map_id when persisting stats - Map analytics queries: get_map_analytics() returns performance metrics, effectiveness scores, and rotation health - API endpoint: GET /api/analytics/maps?range=90d returns summary with best performing map and rotation effectiveness percentage Frontend Changes: - MapAnalyticsView.vue: Complete dashboard with performance charts, sortable metrics table, actionable insights, and CSV export - ECharts bar chart comparing avg vs peak players per map - Color-coded effectiveness scoring (green ≥80%, yellow ≥60%, red <60%) - Time range selector: 30d/90d/all Purpose: Enables data-driven map selection for wipe day based on player engagement metrics. Rotation effectiveness algorithm scores maps by (avg_players / peak_players) * 100. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
7.1 KiB
7.1 KiB
CHANGELOG — Corrosion Admin Panel
All notable changes to this project will be documented in this file.
[Unreleased]
Added (Phase 2.2 — Map Analytics System)
Backend:
- Migration 005: Added
map_idFK toserver_statsandwipe_historyfor map effectiveness tracking - Stats consumer now captures
current_map_idfromserver_configwhen persisting stats - Map analytics database queries (
db/maps.rs):get_map_analytics()— Returns performance metrics per map (avg/peak players, times used, effectiveness score)get_map_population_trends()— Player count trends per map over wipe cycles- Effectiveness scoring algorithm: (avg_players / peak_players) * 100
- Analytics API endpoint (
api/analytics.rs):GET /api/analytics/maps?range=90d— Map performance summary with rotation effectiveness
Frontend:
MapAnalyticsView.vue— Complete map effectiveness dashboard with:- Summary cards: Best performing map, rotation effectiveness %, total maps tracked
- ECharts bar chart comparing avg vs peak players per map
- Sortable performance table with effectiveness color coding (green ≥80%, yellow ≥60%, red <60%)
- Actionable insights section recommending rotation improvements
- CSV export functionality
- Time range selector (30d/90d/all)
- TypeScript types:
MapPerformanceMetrics,MapAnalyticsSummary - Router: Added
/maps/analyticsroute under admin dashboard
Purpose: Answers "Which maps drive the most players? Is my rotation working?" Enables data-driven map selection for wipe day.
Added (Phase 2 — Data Aggregation Pipeline)
Backend:
- Stats ingestion consumer service (
stats_consumer.rs) subscribing tocorrosion.*.statsNATS subject - Complete stats database queries (
db/stats.rs) with support for:- Raw stats insertion and retrieval
- Hourly aggregation queries
- Analytics summary calculations (peak/avg players, uptime)
- Data retention cleanup (7 days raw, 90 days hourly)
- Hourly stats aggregation scheduler job (runs at :05 past every hour)
- Daily cleanup scheduler job (runs at 03:00 UTC)
- Analytics API endpoints (
api/analytics.rs):GET /api/analytics/summary— Peak/avg players, uptime percentageGET /api/analytics/timeseries— Time-series data for charting (hourly/raw granularity)GET /api/analytics/export— CSV export of server stats
- Background service initialization in main.rs (stats consumer + scheduler)
Frontend:
- Analytics TypeScript types (
AnalyticsSummary,TimeseriesData,HourlyStats) - Complete
AnalyticsView.vueimplementation with:- Real-time data fetching from analytics API
- Apache ECharts integration for Player Count and Server Performance charts
- Time range selector (24h/7d/30d)
- CSV export functionality
- Loading states and responsive layout
Infrastructure:
- Made
NatsBridge.jetstreampublic for service consumer access
Added (Sovereign Infrastructure Stack)
Services Deployed:
- Gitea (git.corrosionmgmt.com) — Self-hosted Git with Actions support
- Container:
corrosion-giteaon port 8090 (HTTP) and 8095 (SSH) - SQLite database (self-contained, persistent)
- Replaces GitHub dependency for source control
- Gitea Actions enabled for CI/CD
- Container:
- SeaweedFS (cdn.corrosionmgmt.com) — S3-compatible object storage and CDN
- Container:
corrosion-cdnwith integrated Master/Volume/Filer/S3 - Filer UI at port 8091 (cdn.corrosionmgmt.com)
- Master UI at port 8093 (admin.cdn.corrosionmgmt.com)
- S3 API at port 8092 (internal access)
- Purpose: Map hosting, plugin packages, companion binaries, backups
- Container:
- Gitea Act Runner (asgard build server) — CI/CD execution environment
- Runs on Ryzen 9 7945HX (16C/32T, 64GB DDR5)
- Docker-based job execution
- Go 1.21+ and Rust toolchains available
- Connects to public Gitea instance remotely
CI/CD Workflows:
test-runner.yml— Runner capability validation (hostname, resources, toolchains)build-companion.yml— Production companion agent build pipeline:- Triggers on version tags (v*..)
- Cross-compiles for Linux AMD64 and Windows AMD64
- Generates SHA256 checksums
- Creates Gitea release with auto-generated installation instructions
- Uploads binaries and checksums as release assets
Documentation:
infra/docker-compose.yml— Infrastructure stack definitioninfra/README.md— Deployment guide and architecture overviewinfra/NPM-CONFIG.md— Nginx Proxy Manager configurationinfra/ASGARD-RUNNER.md— Act runner setup guide
Repository Migration:
- Migrated from GitHub to self-hosted Gitea
- Remote updated to
git@git.corrosionmgmt.com:vantzs/corrosion-admin-panel.git - All future development on sovereign infrastructure
Technical Details
Data Flow:
Plugin/Agent publishes stats (60s interval)
→ NATS JetStream (corrosion.*.stats)
→ StatsConsumerService persists to server_stats table
→ Hourly aggregation job rolls up to server_stats_hourly
→ Analytics API queries aggregated data
→ Frontend renders charts via ECharts
Database Schema:
server_statstable (raw stats, 7-day retention)server_stats_hourlytable (aggregated hourly data, 90-day retention)
Scheduler Jobs:
- Hourly aggregation:
0 5 * * * *(at :05 past every hour) - Daily cleanup:
0 0 3 * * *(at 03:00 UTC)
Installation Notes
Frontend:
cd frontend && npm install echarts
Backend:
No additional dependencies beyond existing Cargo.toml.
Deferred to Phase 2.2
- Player retention tracking (new vs returning players, session duration)
- Wipe-correlated analytics
- Player activity heatmaps (time-of-day patterns)
- Anomaly alerting system
[2025-02-15] — Phase 1 Complete
Added (Phase 1 — Foundation)
Backend Services:
- Core control plane (Axum + Tokio)
- Auto-wiper with rollback (
wipe_engine.rs) - Plugin management system
- WebSocket/NATS bridge for real-time data
- Companion agent adapter (bare metal server management)
- Panel adapters (AMP + Pterodactyl)
Frontend:
- Vue 3 dashboard with 19 admin sub-views
- Wipe management UI with real-time progress
- Toast notification system
- Plugin management interface
- Public server site
Infrastructure:
- PostgreSQL schema (migrations 001-003)
- NATS JetStream streams (6 streams configured)
- Docker Compose deployment (4 services)
- JWT auth with refresh tokens, TOTP 2FA
Companion Agent:
- Go binary for bare metal server management
- NATS-based command execution
- Process lifecycle control
- File operations support
uMod Plugin:
- C# plugin for Rust game server integration
- Stats publishing every 60 seconds
- Server lifecycle event reporting
Commits
c5d0571— feat: Complete Phase 1 frontend — WebSocket + Wipe feature end-to-end590765f— feat: Complete Phase 1 backend services and WebSocket/NATS bridge8320591— docs: Update companion agent language choice to Go3c39345— docs: Add CLAUDE.md and Claude Code settings81eeb3b— docs: Add AGENTS.md roster and resource discipline
Format: type: Short description
Types: feat, fix, docs, refactor, test, chore, perf, ci