Monitor your website before users report a problem.
Website monitoring lets PingBeacons regularly check a public website URL, record its status and response time, and track incidents when the website becomes unavailable.
PingBeacons sends checks to your website from outside your application. Your website does not need to send anything back to PingBeacons other than its normal HTTP response.
1. Create a website monitor
Open your dashboard
Sign in to PingBeacons and choose the option to create a new monitor.
Select website monitoring
Choose the website monitor type for a normal public website or web application.
Give the monitor a clear name
Use a name you will immediately recognize later, such as Production Website, Customer Portal, or Marketing Site.
Enter the complete website URL
Enter the public URL that your users actually visit. Include the protocol, preferably HTTPS.
https://example.com/Save the monitor
Once created, PingBeacons can begin checking the website and recording its results.
2. Use a publicly reachable URL
PingBeacons needs to reach the monitored website over the internet. A local development address or private network URL cannot be monitored like a public production website.
Good
A publicly reachable HTTPS production URL.
https://example.com/Not suitable
Localhost and private development URLs that cannot be reached from outside your network.
http://localhost:3000/3. What PingBeacons records
Website checks give you visibility into whether the site is responding and how the monitoring result changes over time.
Current status
See whether the latest monitoring state is healthy or whether a problem has been detected.
Response time
PingBeacons records how long the monitored website took to respond during a check.
Check history
Review previous checks instead of relying only on the current status.
Incidents
When PingBeacons detects a failure, the problem can be tracked as an incident until the website recovers.
4. When your website goes down
A failed website check can move the monitor into a problem state and create an incident. This gives you a record of what happened instead of simply replacing the previous status.
PingBeacons performs a check
The configured website URL is checked.
The check fails
PingBeacons records the failed monitoring result and the monitor can enter a down or problem state.
An incident is recorded
The incident gives you a timeline for the detected outage or failure.
You can receive an alert
PingBeacons uses your notification preferences to determine how to notify you about the incident.
5. Recovery
PingBeacons continues monitoring after a failure. When a later check succeeds, the website can return to a healthy state and the incident can be resolved.
Website becomes available again
Your application or hosting problem is fixed and the website starts responding successfully.
PingBeacons detects the recovery
A subsequent monitoring check succeeds.
The incident is resolved
The recovery is recorded so you can distinguish active problems from previous incidents.
Recovery notification
If enabled in your preferences, PingBeacons can notify you that the monitored website has recovered.
6. Monitor the right URL
The URL you choose determines what PingBeacons is actually testing. Monitor an endpoint that represents the service your users depend on.
If your marketing homepage can stay online while your application is unavailable, monitoring only the homepage may not tell you that the application itself has failed. Consider monitoring important application or API endpoints separately.
7. Review history after an incident
After a problem, use monitor check history and incident history to understand when failures were detected and when the service recovered.
Understand incidents and history