Rename project to OrbitalWard
Add optional TLS certificate expiry checks for website monitors and update product, package, environment, Docker, and documentation naming.
This commit is contained in:
+15
-16
@@ -1,10 +1,10 @@
|
||||
# InfraPulse Progress
|
||||
# OrbitalWard Progress
|
||||
|
||||
Last updated: 2026-05-22
|
||||
Last updated: 2026-05-23
|
||||
|
||||
## Current State
|
||||
|
||||
InfraPulse has a working Docker Compose development stack with PostgreSQL, Redis, FastAPI backend, Python worker, and React/Vite frontend.
|
||||
OrbitalWard has a working Docker Compose development stack with PostgreSQL, Redis, FastAPI backend, Python worker, and React/Vite frontend.
|
||||
|
||||
Implemented foundation:
|
||||
|
||||
@@ -18,6 +18,7 @@ Implemented website-monitor slice:
|
||||
|
||||
- Create, edit, delete website monitors from the UI.
|
||||
- HTTP status and expected-text checks.
|
||||
- Optional TLS certificate expiry checks for HTTPS monitors.
|
||||
- Monitor status and recent incident visibility on dashboard.
|
||||
- Basic alert rules created with website monitors.
|
||||
- Incidents can be acknowledged and silenced from the UI.
|
||||
@@ -27,7 +28,7 @@ Implemented notification slice:
|
||||
|
||||
- Create, edit, test, and delete notification channels from the UI.
|
||||
- Generic webhook, Mattermost, and Zoom Team Chat channel types.
|
||||
- Webhook URLs encrypted at rest using `INFRAPULSE_SECRET_KEY`.
|
||||
- Webhook URLs encrypted at rest using `ORBITALWARD_SECRET_KEY`.
|
||||
- Saved webhook URLs are not returned to the UI.
|
||||
- Configurable post username per notification channel.
|
||||
- Worker sends incident open and recovery notifications.
|
||||
@@ -42,7 +43,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.
|
||||
- TLS certificate expiry checks 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.
|
||||
@@ -51,16 +51,15 @@ Implemented notification slice:
|
||||
|
||||
## Recommended Next Work
|
||||
|
||||
1. Add TLS certificate expiry monitor support.
|
||||
2. Add ping and TCP port monitors.
|
||||
3. Add alert rule editing UI and richer alert conditions.
|
||||
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 backend and worker tests for the website-monitor and notification flows.
|
||||
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.
|
||||
|
||||
## Operational Notes
|
||||
|
||||
@@ -75,4 +74,4 @@ Default local login comes from `.env`:
|
||||
- `INITIAL_ADMIN_EMAIL=admin@example.com`
|
||||
- `INITIAL_ADMIN_PASSWORD=change-me`
|
||||
|
||||
Change these values before using InfraPulse outside local development.
|
||||
Change these values before using OrbitalWard outside local development.
|
||||
|
||||
Reference in New Issue
Block a user