View Monitored Service Status
Read Eenos service state, uptime, memory and monitoring participation, refresh the status table and distinguish running services from enabled recovery policy.
Open System → Service Monitor → Service Status. This is a status table; it does not provide start, stop or restart actions.
Table fields
| Field | Meaning |
|---|---|
| Service | Display name and configured service-manager unit. |
| Status | Running, Stopped or Unknown, with underlying state text. |
| State Since | When the reported state began, when available. |
| Uptime / Downtime | Duration associated with the reported state. |
| Memory Usage | Reported service memory, or Unknown. |
| Monitoring | Whether monitoring is enabled for this service entry. |
The table maps active state text to Running. Inactive, failed and deactivating states appear as Stopped; other states appear as Unknown. Inspect the underlying state text to distinguish failure from an intentional stop or transition.
Search or sort to locate a service. The initial page size is 25. Choose Refresh to reload without resetting the current table page. The page also reloads data approximately every 30 seconds; this display refresh is independent of the background monitor's configured check interval.
Interpret monitoring separately
A Running service can have monitoring disabled. An Enabled service can still be stopped or failed, and global monitoring must also be on for automatic checks. The Monitoring column shows the individual entry's setting; it is not a combined indicator of global policy or monitor-daemon health.
Saved monitoring entries can remain in the inventory even when the corresponding installation or unit needs attention. An empty table or Unknown values should prompt a configuration/status investigation, not an assumption that no service needs monitoring.
Process state is only one check
Running does not prove websites respond, mail delivers, databases accept the intended queries or applications work. Verify the affected function and review detailed diagnostics before treating an incident as resolved.
Use Monitor Settings to change recovery policy and Service Restart for a deliberate manual service operation. Coordinate those actions so automatic monitoring does not conflict with planned downtime.