System KPI and runtime status
The core landing page now serves a live status view instead of a 404 so you can quickly confirm the service is up, check uptime, and spot recent application errors without opening the logs.
Best practice: keep this page lightweight, expose full stack traces only in private logs, and rely on
/up or /health for automated probes.
Core health summary
Quick status indicators for the running core instance.
| Host | cp31-jhb.za-dns.com |
|---|---|
| Process ID | 1793357 |
| Last heartbeat | 2026-11-01 10:48:32 |
| Database driver | mysql |
| Database name | chedadig_ngamicore |
| Database latency | 1 ms |
Health probes
Use these for monitoring and quick validation.
For production, wire this page to a supervisor, container, or uptime monitor so uptime reflects the actual process lifecycle.
Latest application errors
Only active errors from the current runtime window are shown here. Full traces stay in the log file.