Monitoring
Monitoring checks a chosen website, service or scheduled-job heartbeat even when there are no visitor sessions. It reports check results and incidents; it does not restart a service, renew a certificate or repair your site.
Set up a check
- Open Monitoring in the project and choose the check that matches the question you want answered.
- Enter the target and configure the interval and available validation options. Check that the target is intended to be reachable from outside your own session/network.
- Activate the monitor and wait for its first result. Review recent checks before relying on an alert.
- Configure available notification preferences and integrations for the people who should act.
| Type | Question it answers |
|---|---|
| HTTP / API | Does the selected endpoint respond according to the configured check? |
| SSL | Is the certificate valid, and when does it expire? |
| Domain | What renewal/registry information is available? |
| Cron heartbeat | Did the scheduled job report within its expected interval and grace period? |
| DNS | Does the host resolve? |
| TCP port | Can a connection be made to the selected port? |
| Ping | Does the host respond to the supported reachability check? |
How Pintelly behaves
Checks run at the configured cadence; a short failure between checks may not be observed. A paused monitor stops active checks. Changes can take until a subsequent check to appear in the result.
Cron monitoring relies on your job sending the provided heartbeat. Place that signal at the point that represents the outcome you intend to monitor; sending it before work is done can make a failed job appear to have checked in. Keep the heartbeat URL private.
Availability and response-time reports describe completed checks for the selected period. Missing checks are not evidence of uptime. A responding endpoint does not prove that every part of a user flow works, and a valid certificate does not confirm that the application is healthy.
Investigate a failure
Open the incident/check detail and compare the target, timestamps and observed response. Review recent changes and your site's access restrictions. Security challenges, rate limits, a private-network target or a deliberately blocked port can cause external checks to fail while your own browser still works.
Allow legitimate checks only for intended targets; do not disable broad protections just to turn a monitor green. For a late cron check, inspect the job's last execution, heartbeat placement, expected interval and grace period. For certificate/domain warnings, verify the reported expiry and arrange renewal through your provider.