a00247bc74
chore: convert guru-connect to submodule; integrate ADR-008 + 2026-05-29 session log
...
guru-connect is now tracked as a submodule (azcomputerguru/guru-connect @ e3e95f8);
its working state was published to the GC repo first, so no content is lost. guru-rmm
advanced to include ADR-008 (GC integration boundary) replayed on top of the team's
Integrations Center / discovery advances. Includes the native-remote-control spec
(now inside the GC submodule), the versionable-products memory, and the session log.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com >
2026-05-29 06:36:54 -07:00
8521c95755
Phase 1 Week 2: Infrastructure & Monitoring
...
Added comprehensive production infrastructure:
Systemd Service:
- guruconnect.service with auto-restart, resource limits, security hardening
- setup-systemd.sh installation script
Prometheus Metrics:
- Added prometheus-client dependency
- Created metrics module tracking:
- HTTP requests (count, latency)
- Sessions (created, closed, active)
- Connections (WebSocket, by type)
- Errors (by type)
- Database operations (count, latency)
- Server uptime
- Added /metrics endpoint
- Background task for uptime updates
Monitoring Configuration:
- prometheus.yml with scrape configs for GuruConnect and node_exporter
- alerts.yml with alerting rules
- grafana-dashboard.json with 10 panels
- setup-monitoring.sh installation script
PostgreSQL Backups:
- backup-postgres.sh with gzip compression
- restore-postgres.sh with safety checks
- guruconnect-backup.service and .timer for automated daily backups
- Retention policy: 30 daily, 4 weekly, 6 monthly
Health Monitoring:
- health-monitor.sh checking HTTP, disk, memory, database, metrics
- guruconnect.logrotate for log rotation
- Email alerts on failures
Updated CHECKLIST_STATE.json to reflect Week 1 completion (77%) and Week 2 start.
Created PHASE1_WEEK2_INFRASTRUCTURE.md with comprehensive planning.
Ready for deployment and testing on RMM server.
2026-01-17 20:24:32 -07:00
