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

Add alert rule editing UI

Browse Source
This commit is contained in:
Keith Smith
2026-05-23 16:08:27 -06:00
parent a8a4eb84f6
commit 5c9f93692a
10 changed files with 340 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/agent-handoff.md
+1 -1
View File
@@ -76,7 +76,7 @@ Issue source docs:
- `docs/progress.md`
- `docs/roadmap.md`
Current completed items include TLS expiry monitor support, HTTP/website checks, ping and TCP port checks, basic alert evaluation, incident actions, and webhook notification channels. The next recommended implementation issue is alert rule editing UI, followed by guided SNMP discovery and monitor selection.
Current completed items include TLS expiry monitor support, HTTP/website checks, ping and TCP port checks, basic alert evaluation, alert rule editing UI, incident actions, and webhook notification channels. The next recommended implementation issue is SNMP credential profiles and guided SNMP discovery, followed by SNMP monitor selection.
## Guardrails
docs/progress.md
+20 -11
View File
@@ -41,13 +41,22 @@ Implemented notification slice:
- Worker sends incident open and recovery notifications.
- Notification state/history is stored in incident details to avoid duplicate sends.
Implemented alerting management slice:
- Alerts page lists alert rules separately from incidents.
- Alert rules can be enabled, disabled, and edited from the UI.
- Editable alert rule fields include friendly name, severity, failure threshold, and cooldown.
- HTTPS website alert rules expose TLS certificate expiry check and warning-day controls.
- Existing simple alert conditions are shown in friendly language instead of raw condition data.
- Worker honors alert rule cooldown before opening a new incident for a recently-triggered rule.
## Known Gaps
- Credential vault UI and real credential encryption workflows are not complete.
- Audit logging tables exist, but events are not consistently written yet.
- User management UI is not implemented.
- Role management is basic and needs full admin flows.
- Alert rule editing UI is not implemented.
- Richer alert condition editing is not implemented yet.
- Guided SNMP device discovery and friendly SNMP monitor selection are not implemented yet.
- SNMP credential profiles, interface status, traffic counters, errors, uptime, CPU, and memory checks are not implemented yet.
- Notification routing/policies are not implemented; all enabled webhook channels receive incident notifications.
@@ -59,16 +68,16 @@ Implemented notification slice:
## Recommended Next Work
1. Add alert rule editing UI and richer alert conditions.
2. Add SNMP credential profiles and guided SNMP device discovery.
3. Add SNMP discovery selection UI to choose what to monitor and alert on.
4. Add SNMP interface status, traffic, errors, uptime, CPU, and memory collection.
5. Add notification policy/routing controls.
6. Add email/SMTP notification channel.
7. Add audit event writes for auth, monitor, credential, notification, and incident actions.
8. Build credential vault UI with masked secret handling.
9. Add user administration UI.
10. Add graphs for website response time and monitor status history.
1. Add SNMP credential profiles and guided SNMP device discovery.
2. Add SNMP discovery selection UI to choose what to monitor and alert on.
3. Add SNMP interface status, traffic, errors, uptime, CPU, and memory collection.
4. Add notification policy/routing controls.
5. Add email/SMTP notification channel.
6. Add audit event writes for auth, monitor, credential, notification, and incident actions.
7. Build credential vault UI with masked secret handling.
8. Add user administration UI.
9. Add graphs for website response time and monitor status history.
10. Add richer alert condition editing.
11. Add backend and worker tests for the website-monitor and notification flows.
## Operational Notes