Save a public target
LoopAware validates the monitor target and rejects private, loopback, link-local, and special-use addresses.
Uptime monitoring
Uptime checks beside feedback and traffic
LoopAware health monitoring runs backend synthetic GET probes against configured public HTTP(S) targets. Site operators can set interval, timeout, failure threshold, manual checks, and alert recipients without adding another monitoring surface to the workflow.
The problem
Small product sites often discover outages indirectly: a confused customer submits feedback, traffic drops, or an error report appears after the page is already unreachable. LoopAware adds a direct public-target check to the same site record that already holds feedback, subscribers, traffic, and LA Sentry issues.
How it works
Set thresholds
Operators configure interval, timeout, and consecutive-failure threshold so one failed probe does not automatically become an outage alert.
Alert the right people
Alerts can go to the manager, whole team, or selected site members through the configured Pinguin email path.
Feature-to-benefit fit
Public-target validation
Prevents saving targets that should not be probed from a backend health checker.
Manual check
Lets an owner confirm the current state from the dashboard after changing DNS, deploys, or site settings.
Recovered alerts
Operators can see both failure and recovery transitions instead of only receiving the first down message.
Use-case examples
Marketing site uptime
Monitor the public landing page that also hosts the feedback widget, subscribe form, and traffic pixel.
Agency client checks
Configure one monitor per client site and keep recipients aligned with per-site team membership.
Post-deploy validation
Run an immediate check after a release to confirm the target responds before traffic reports and feedback are reviewed.
Objections and limitations
- LoopAware does not guarantee uptime or replace a full incident-management platform.
- Health checks are backend synthetic GET probes, not a customer-site heartbeat script.
- Alerts depend on configured Pinguin email delivery and are emitted on state transitions after the saved threshold.
Pair health checks with server-side error capture when you need both availability and application failure context.
Implementation checklist
- Choose the public target URL, request method, and threshold that reflect the site surface customers actually depend on.
- Run a manual check before relying on automated down and recovered notifications.
- Confirm recipients are set to the manager, team, or selected members who should respond to incidents.
Common questions
When should teams use this uptime monitoring guide?
Use LoopAware health checks to monitor public site targets with validation, thresholded down and recovered states, team recipients, and email alerts. It is a fit when a small team needs simple availability checks tied to the same managed LoopAware site.
What should teams verify after setup?
Confirm the workflow is tied to the correct LoopAware site, then check the first dashboard records with the people who will act on them.
Add availability to the same site record
Use the Health tab when the question is not only what visitors said, but whether the page was reachable in the first place.