25 lines
1.2 KiB
Markdown
25 lines
1.2 KiB
Markdown
# OrbitWard Vision
|
|
|
|
OrbitWard is a secure, self-hosted monitoring platform for homelabs, small businesses, and internal IT teams.
|
|
|
|
The v0.1 product should feel like a polished appliance, not a pile of raw monitoring configuration. Users should be guided through adding targets, testing connections, discovering useful items, choosing what to monitor, and separately choosing what should alert.
|
|
|
|
## Design Philosophy
|
|
|
|
OrbitWard exposes intent, not implementation details.
|
|
|
|
Raw SNMP OIDs, probe internals, and collector details belong behind friendly profiles and advanced tools. The normal UI should say things like "Port 5 outbound traffic", "Graph this port", and "Alert if port goes down".
|
|
|
|
## Initial Scope
|
|
|
|
The initial release targets:
|
|
|
|
- Authentication and roles
|
|
- Assets, monitors, alert rules, incidents, credentials, and notification channels
|
|
- Website checks for HTTP status, expected text, and TLS expiry
|
|
- Dashboard status views
|
|
- Mattermost, Zoom Team Chat, email, and generic webhook notifications
|
|
- Foundations for guided discovery and plugins
|
|
|
|
Advanced NMS features such as topology, traps, syslog, NetFlow, distributed pollers, and config backup are future work.
|