laantungir/ngit-grasp
1
0
Fork 0
mirror of https://relay.ngit.dev/npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr/ngit-grasp.git synced 2026-10-05 23:18:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

issue: update 573b - diagnostics improvements deployed, baseline collection started

Browse Source
This commit is contained in:
DanConwayDev
2026-01-17 23:49:18 +00:00
parent 9343932e7a
commit 2b4ac4e07b
1 changed files with 42 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
573b-production-timeout-diagnosis.md
+42
View File
@@ -449,6 +449,30 @@ Currently relay.ngit.dev runs ngit-relay (reference implementation). Before migr
- Need to create separate issue for migration planning
- Next: Create issue for relay.ngit.dev migration, focus on ngit-grasp observability
### 2026-01-17 [Session 23:30] - Diagnostics Improvements Deployed
- Completed: Enhanced diagnostics infrastructure and documentation
- Tasks:
1. ✅ Fixed connection counting in baseline script (port-based, not PID-based)
2. ✅ Added container stats collection (via systemd-run for proper cgroup access)
3. ✅ Added connection state breakdown (ESTABLISHED, TIME_WAIT, CLOSE_WAIT, etc.)
4. ✅ Created comprehensive MONITORING.md documentation
5. ✅ Deployed improvements to all three relays (gitnostr.com, relay.ngit.dev, ngit.danconwaydev.com)
6. ✅ Verified all relays working with enhanced metrics
- Deployment Results:
- All three relays now collecting accurate connection counts per service
- Container stats (CPU, memory, network I/O) now available for Docker-based services
- Connection state breakdown provides visibility into connection lifecycle
- MONITORING.md provides comprehensive guide for interpreting metrics
- Baseline Collection Status:
- Started: 2026-01-17 23:30 UTC
- Duration: 36 hours (until 2026-01-19 11:30 UTC)
- Enhanced metrics: Connection counts, container stats, state breakdown
- Purpose: Establish baseline before relay.ngit.dev migration (issue 820a)
- Next Steps:
1. Check baseline collection at 10-minute mark (verify data quality)
2. Review baseline data after 36 hours
3. Use baseline for relay.ngit.dev migration decision (issue 820a)
### 2026-01-16 [Phase 0 Step 1 - Initial Scripts]
- Completed: Created three bash diagnostic scripts
- Issue: Scripts not compatible with NixOS declarative philosophy
@@ -535,3 +559,21 @@ Currently relay.ngit.dev runs ngit-relay (reference implementation). Before migr
- ngit-relay instances (gitnostr.com, relay.ngit.dev)
- ngit-grasp (ngit.danconwaydev.com)
- Supporting infrastructure (nginx, etc.)
## Next Steps
1. **10-Minute Check (2026-01-17 23:40 UTC):**
- Verify baseline collection is running on all three relays
- Check data quality (connection counts, container stats, state breakdown)
- Ensure no errors in collection scripts
2. **36-Hour Review (2026-01-19 11:30 UTC):**
- Analyze baseline data patterns
- Compare metrics across all three relays
- Identify any anomalies or trends
- Document findings for relay.ngit.dev migration decision
3. **Migration Decision (Issue 820a):**
- Use baseline data to inform relay.ngit.dev migration
- Determine if accelerated migration plan is viable
- Set timeline for migration execution