Feature
Uptime monitoring, SSL and a public status page
A probe every five minutes, latency history, an alert before the certificate expires, and a public status page to share.
The installation, in full
composer require quiet-guard/laravel-monitor
The problem
An application that is down raises no exception: a server that stopped answering has nobody left to report the error. And a certificate that expires on a Sunday morning locks everyone out at the same moment, with no warning.
What you get
- Seven days of latency history, with gaps where the site was down rather than zeroes
- A public status page at the address of a token, never indexable
- A badge to drop in your README
- Seven-day availability, day by day
- The outage windows listed, not just a percentage
- The probed address, which never appears on the public page
- Once switched on, a daily check for exposed sensitive files (.env, .git, Telescope...), keeping nothing the site answers
How it works
01
An HTTP probe, every five minutes
Status under 400, latency recorded, with the same anti-SSRF guards as the webhooks: an internal address is never probed.
02
An alert per transition, not per probe
You hear when it goes down and when it comes back. Never every five minutes in between.
03
The certificate read directly
At fourteen days and again at three, once each. A renewal resets the cycle on its own.