# 4. System Health User Type: **Super Administrator** Source: *Mi Digital Academy - Education CRM Features Document* --- ## 4. System Health ### 4.1 System Health Monitoring **What it does:** Monitors the system health: the health of the system (the health, the status, the metric, the value, the date) is monitored, so the system is visible (the monitoring is the watch). The Super Administrator views the system health monitoring (the health, the status, the metric, the value, the date) so the monitoring is structured and the health is explicit. **Sub-features:** - System health: the health (the health of the system, the status, the metric, the value) - Health status: the status (the healthy, the warning, the critical) - Health metric: the metric (the metric of the health, e.g., the CPU, the memory) - Health value: the value (the value of the metric, e.g., the percentage) - Health period: the period (the period of the health, e.g., the current, the hourly) - Health view: the view (the health, the statuses, the metrics, the period) - Health export: the export (the health, the format, the period) - Audit logging of the system health monitoring **Super Administrator User Journey:** 1. Super Admin views the system health monitoring: the health (the health of the system, the status, the metric, the value), the statuses (the healthy, the warning, the critical), and the period (the period of the health); the monitoring is explicit. 2. Views the health status: the status (the healthy, the warning, the critical); the status is the state. 3. Views the health metric: the metric (the metric of the health, e.g., the CPU, the memory); the metric is the measure. 4. Views the health value: the value (the value of the metric, e.g., the percentage); the value is the result. 5. Sets the health period: the period (the period of the health, e.g., the current, the hourly); the period is the scope. 6. Exports the health: the export (the health, the format, the period); the export is the record. 7. The health is visible: the health, the statuses, the metrics, the period, so the monitoring is complete. 8. The system health monitoring is audit-logged with the health, the status, and the timestamp. **Rules & Edge Cases:** - The system health is the state (the health of the system, the status, the metric, the value); the health is the condition. - The health status is the control (the healthy, the warning, the critical); the status is the gate. - The health metric is the measure (the metric of the health, e.g., the CPU, the memory); the metric is the value. - The health value is the result (the value of the metric, e.g., the percentage); the value is the outcome. - The health is visible (the health, the statuses, the metrics, the period); the monitoring is managed. - System health monitoring is audit-logged with the health, status, and timestamp. ### 4.2 Uptime Status **What it does:** Shows the uptime status: the uptime of the system (the uptime, the status, the percentage, the period) is shown on the dashboard, so the uptime is visible (the overview is the summary). The Super Administrator views the uptime status (the uptime, the status, the percentage, the period) so the viewing is structured and the status is explicit. **Sub-features:** - Uptime: the uptime (the uptime of the system, the percentage, the period) - Uptime status: the status (the up, the down, the degraded) - Uptime percentage: the percentage (the percentage of the uptime, e.g., the 99.9%) - Uptime period: the period (the period of the uptime, e.g., the daily, the weekly, the monthly) - Uptime trend: the trend (the trend of the uptime, the period, the change) - Uptime view: the view (the uptime, the statuses, the percentages, the period) - Uptime export: the export (the uptime, the format, the period) - Audit logging of the uptime status viewing **Super Administrator User Journey:** 1. Super Admin views the uptime status: the uptime (the uptime of the system, the percentage, the period), the statuses (the up, the down, the degraded), and the period (the period of the uptime); the status is explicit. 2. Views the uptime status: the status (the up, the down, the degraded); the status is the state. 3. Views the uptime percentage: the percentage (the percentage of the uptime, e.g., the 99.9%); the percentage is the measure. 4. Sets the uptime period: the period (the period of the uptime, e.g., the daily, the weekly, the monthly); the period is the scope. 5. Views the uptime trend: the trend (the trend of the uptime, the period, the change); the trend is the direction. 6. Exports the uptime: the export (the uptime, the format, the period); the export is the record. 7. The uptime is visible: the uptime, the statuses, the percentages, the period, so the status is complete. 8. The uptime status viewing is audit-logged with the uptime, the status, and the timestamp. **Rules & Edge Cases:** - The uptime is the availability (the uptime of the system, the percentage, the period); the uptime is the measure. - The uptime status is the state (the up, the down, the degraded); the status is the control. - The uptime percentage is the value (the percentage of the uptime, e.g., the 99.9%); the percentage is the measure. - The uptime trend is the direction (the trend of the uptime, the period, the change); the trend is the insight. - The uptime is visible (the uptime, the statuses, the percentages, the period); the viewing is managed. - Uptime status viewing is audit-logged with the uptime, status, and timestamp. ### 4.3 Error and Incident Overview **What it does:** Shows the error and incident overview: the errors (the error, the type, the count, the date) and the incidents (the incident, the type, the count, the date) are shown on the dashboard, so the errors and incidents are visible (the overview is the summary). The Super Administrator views the error and incident overview (the error, the incident, the type, the count, the date) so the viewing is structured and the overview is explicit. **Sub-features:** - Error: the error (the error, the type, the count, the date) - Incident: the incident (the incident, the type, the count, the date) - Error count: the count (the count of the errors) - Incident count: the count (the count of the incidents) - Error status: the status (the open, the resolved, the pending) - Error period: the period (the period of the errors, e.g., the daily, the weekly, the monthly) - Error view: the view (the errors, the incidents, the counts, the period) - Audit logging of the error and incident viewing **Super Administrator User Journey:** 1. Super Admin views the error and incident overview: the errors (the error, the type, the count, the date), the incidents (the incident, the type, the count, the date), and the period (the period of the errors); the overview is explicit. 2. Views the error count: the count (the count of the errors); the count is the measure. 3. Views the incident count: the count (the count of the incidents); the count is the measure. 4. Views the error status: the status (the open, the resolved, the pending); the status is the state. 5. Sets the error period: the period (the period of the errors, e.g., the daily, the weekly, the monthly); the period is the scope. 6. Exports the errors: the export (the errors, the format, the period); the export is the record. 7. The errors and incidents are visible: the errors, the incidents, the counts, the period, so the overview is complete. 8. The error and incident viewing is audit-logged with the error, the status, and the timestamp. **Rules & Edge Cases:** - The error is the fault (the error, the type, the count, the date); the error is the problem. - The incident is the event (the incident, the type, the count, the date); the incident is the occurrence. - The error count is the measure (the count of the errors); the count is the volume. - The error status is the state (the open, the resolved, the pending); the status is the control. - The errors and incidents are visible (the errors, the incidents, the counts, the period); the viewing is managed. - Error and incident viewing is audit-logged with the error, status, and timestamp.