ksmith/OrbitWard
1
0
Fork 0
Code Issues 12 Pull Requests Actions Packages Projects Releases Wiki Activity

Add ping and TCP monitor types

Browse Source 
Adds ping and TCP monitor creation APIs, worker collectors, network checks UI, dashboard monitor status support, and progress documentation.
This commit is contained in:
Keith Smith
2026-05-23 15:01:57 -06:00
parent 597ff18c2a
commit 16932957b2
13 changed files with 577 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/progress.md
+15 -10
View File
@@ -24,6 +24,13 @@ Implemented website-monitor slice:
- Incidents can be acknowledged and silenced from the UI.
- Deleting a monitor resolves any open incidents tied to that monitor.
Implemented network-monitor slice:
- Create, edit, delete ping and TCP port monitors from the UI.
- Worker performs ICMP ping checks and TCP connection checks.
- Ping and TCP monitors use the same alert rule, incident, recovery, and notification flow as website monitors.
- Dashboard monitor status includes website, ping, and TCP monitors.
Implemented notification slice:
- Create, edit, test, and delete notification channels from the UI.
@@ -43,7 +50,6 @@ Implemented notification slice:
- Alert rule editing UI is not implemented.
- Notification routing/policies are not implemented; all enabled webhook channels receive incident notifications.
- Email/SMTP notifications are not implemented yet.
- Ping and TCP checks are not implemented yet.
- Graphing exists only as placeholders; metric visualization is not implemented.
- Worker scheduling is simple polling, not a Redis queue yet.
- Tests are still minimal and need meaningful backend/worker/frontend coverage.
@@ -51,15 +57,14 @@ Implemented notification slice:
## Recommended Next Work
1. Add ping and TCP port monitors.
2. Add alert rule editing UI and richer alert conditions.
3. Add notification policy/routing controls.
4. Add email/SMTP notification channel.
5. Add audit event writes for auth, monitor, credential, notification, and incident actions.
6. Build credential vault UI with masked secret handling.
7. Add user administration UI.
8. Add graphs for website response time and monitor status history.
9. Add backend and worker tests for the website-monitor and notification flows.
1. Add alert rule editing UI and richer alert conditions.
2. Add notification policy/routing controls.
3. Add email/SMTP notification channel.
4. Add audit event writes for auth, monitor, credential, notification, and incident actions.
5. Build credential vault UI with masked secret handling.
6. Add user administration UI.
7. Add graphs for website response time and monitor status history.
8. Add backend and worker tests for the website-monitor and notification flows.
## Operational Notes