MatrixEasyMode / Roadmap / v0.1.2
v0.1.2: monitoring, health, and operator alerts
The v0.1.2 roadmap focuses on helping operators notice important system conditions earlier: health checks, degraded states, alert routing, and multi-channel notifications.
v0.1.1 focuses on operational safety and control. v0.1.2 is expected to build on that foundation by improving how operators understand the health of a running Matrix + Element stack over time.
Once a Matrix stack is deployed, operators need to know when something requires attention. Silent failure is one of the most dangerous modes for self-hosted infrastructure.
The goal is not to create noisy notifications for every minor event. The goal is to surface meaningful operational signals early enough for the person responsible for the system to respond before small problems become larger failures.
Operating principle
MatrixEasyMode should help operators move from reactive troubleshooting toward visible, understandable, and timely system awareness. Good alerting should reduce uncertainty, not create noise.
Planned scope
What v0.1.2 is expected to focus on
The current scope is focused on operator-facing health visibility, alert routing, and notification channels for conditions that require attention.
Operator health overview
Provide a clearer health summary for the running Matrix + Element stack so operators can quickly understand whether core services need attention.
Runtime and dependency checks
Surface important runtime conditions around services, database connectivity, ingress reachability, certificates, configured hostnames, and other dependencies that affect operation.
Alert routing and severity
Move toward clearer alert severity and routing so operators can distinguish informational events from degraded states, security-sensitive events, and urgent conditions.
Email alerts
Support email-based operator notifications for important system events, degraded health states, and administrative issues that require attention.
Matrix and Telegram alerts
Explore Matrix and Telegram as practical notification channels for operators who already use chat-based workflows for infrastructure awareness.
Text message alerts
Explore text-message alerting for higher-urgency operational events where email or chat notifications may not be enough.
Administrative and security alerts
Surface important administrative and security-related events such as admin login activity, recovery events, token changes, and emergency-control usage.
Alert noise control
Avoid treating every event as equally urgent. Alerting should help operators understand what matters, not create a constant stream of low-value noise.
Intended operator outcomes
The purpose of this release is not to add notification channels for their own sake. The purpose is to make important system conditions easier to see, understand, and respond to.
What this release is not trying to do
v0.1.2 is not intended to create noisy alert spam or hide the real system behind a single green checkmark. Some degraded states need to be visible because they affect federation, access, recovery, security, and operator confidence.
Scope may change
This roadmap describes the current direction for v0.1.2. Some items may move, split, or change as implementation work reveals better release boundaries. The priority is to ship useful, documented, operator-facing visibility rather than add noisy notifications for their own sake.