The Monitor page shows, live, what LaraMonster uses on your computer and which sites are busy, with recommendations when things get heavy. The Logs page has every log LaraMonster and its services write.
Monitor
Updated every 2 seconds:
| Section | Shows |
|---|---|
| Tiles | LaraMonster's memory and CPU (and how many processes), next to the whole computer's memory, swap and CPU load |
| Recommendations | What to switch off when something uses an unusual amount of CPU or memory, like an idle database or a forgotten queue worker |
| What's using resources | Each part (web server, each PHP pool, each service, workers) with its CPU and memory, and actions to stop or restart it |
| Busiest sites | Requests per minute and CPU for each site that got a request in the last minute |
The sidebar shows a count on Monitor when there's a recommendation.
Logs
Pick a log on the Logs page to see its newest lines; it keeps following while you watch. From the terminal:
$ laramonster logs # list the logs
$ laramonster logs caddy -f # follow the web server
$ laramonster logs php84-fpm -n 300
$ laramonster logs mysql| Log | Look here when |
|---|---|
laramonster | The engine won't start, a reload fails, a warning appears |
caddy | A site doesn't answer, certificates, proxies |
php<version>-fpm | 502 errors, PHP crashing, extensions that won't load |
mysql, postgres, redis… | A service won't start |
The files themselves are in logs/ inside the LaraMonster home folder; the tray menu's Open logs folder opens it. Your app's own storage/logs/laravel.log is in the Debugger.