Open Monitoring & Logs
In the EPAdmin administrator workspace, open Monitoring & Logs or search the exact tool label. Dated observations and bounded scoped logs do not establish a full historical monitoring suite. Read the detailed operational guide before making changes. The table lists every requested leaf in this group. A connected destination remains subject to current local permissions, resource ownership, installed capability, licence and fresh verification. It is not a production acceptance claim.
Complete tool reference
| Tool | Destination and behavior | Permission or limitation |
|---|---|---|
| Server Monitoring | Server → Builder | Any listed local Admin grant: server:read, server:manage |
| CPU / RAM History | Unavailable in this checkpoint | Persistent CPU/RAM time-series history is not implemented; the live sampled snapshot is available. |
| Disk I/O Monitoring | Server → Builder; server accounts section | Any listed local Admin grant: server:read, server:manage |
| Bandwidth Reports | Server → Builder; server traffic section | Any listed local Admin grant: server:read, server:manage |
| Apache Logs | Websites; choose the authorized website first; Logs tab | Any listed local Admin grant: hosting:read, hosting:manage |
| Mail Logs | ServerLogs → Services | Any listed local Admin grant: server:read, server:manage |
| Security Logs | ServerLogs → Security | Any listed local Admin grant: security:read, security:manage |
| System Logs | ServerLogs → Services | Any listed local Admin grant: server:read, server:manage |
| Alert Configuration | Unavailable in this checkpoint | Alert display/delivery exists; custom threshold and quiet-window configuration is not implemented. |
Make and verify a change
Select the intended owned resource and load its current detail. Read impact, current revision, applicable preview and confirmation before an explicit submission. If the server requires fresh authentication, complete its password/MFA flow and submit the reviewed request again; no write is automatically replayed. Keep the durable operation ID and inspect the final resource/service state.
When a tool is missing or denied
Check the current role/grants, installed version and actual capability. A menu label marked unavailable has no supported action to force. Source updates can be newer than your installed kit; they do not automatically add hosting acceptance. Preserve the safe operation/correlation reference and inspect original state before retrying an interrupted change. Do not disable confinement, modify private journals or substitute another account to bypass denial.