Understand what happened and when.
PingBeacons keeps monitoring activity and incidents visible so you can understand when a problem was detected, review previous checks, and see when a monitored service recovered.
A service may be healthy now even though it experienced an outage earlier. Check and incident history help you understand what happened before the current state.
1. Monitor check history
Website and API monitoring produces check results over time. These results let you look beyond the latest status.
Successful checks
Successful checks indicate that the monitored target responded successfully at that point in time.
Failed checks
Failed results help identify when PingBeacons detected a problem with the monitored target.
Response time
Website and API checks can include response-time information so you can review how quickly the endpoint responded.
Previous activity
Browse older monitoring results when investigating behavior that happened before the latest check.
2. What is an incident?
An incident represents a monitoring problem detected by PingBeacons. It gives the failure a lifecycle instead of showing only a temporary down status.
The monitor is healthy
Normal checks are succeeding and there is no active problem.
A failure is detected
A monitoring result indicates that the target is no longer in its expected healthy state.
An incident is recorded
PingBeacons records the problem so you can identify when the incident began.
The service recovers
When a later monitoring result is healthy again, the incident can be resolved and the recovery is recorded.
3. Active vs resolved incidents
Active incident
The monitor currently has a detected problem that has not yet been followed by a successful recovery.
Resolved incident
The monitored service recovered and the previous incident is no longer active.
4. Recovery tracking
PingBeacons continues monitoring after detecting a problem. This allows a later successful result to show that the service recovered.
Problem detected
The monitor enters a problem state and an incident is active.
Monitoring continues
PingBeacons keeps evaluating the monitored target rather than stopping after the first failure.
A healthy result returns
A later monitoring result indicates that the service is responding normally again.
Recovery is recorded
The active incident is resolved and its history remains available for later review.
5. Using history to investigate an outage
When you receive an alert, the monitor detail and history can help you establish a basic timeline before investigating your application or infrastructure.
Check the current monitor status
First determine whether the problem is still active or whether the service has already recovered.
Review recent checks
Look at the monitoring results around the time the problem was detected.
Open the incident
Use the incident information to understand when the detected problem began and whether it has been resolved.
Compare with your own logs
Use the PingBeacons timeline alongside server, application, database, deployment, or hosting logs to investigate the root cause.
Monitoring can tell you that a service failed or recovered, but finding the underlying cause may require your application and infrastructure logs.
6. Response time history
A service does not always fail completely. Response-time information can also help you notice when an endpoint was responding more slowly than expected.
It shows the response observed by a PingBeacons monitoring check. Use application performance monitoring, server metrics, and logs when you need deeper performance diagnosis.
7. Heartbeat history is different
Heartbeat monitoring is based on signals received from your scheduled job rather than normal outbound website checks.
Website / API
PingBeacons performs the check and records when the target was checked.
Heartbeat
Your job contacts PingBeacons, so the important activity is when the latest heartbeat was received.
8. Notifications and incidents
Incident and recovery notifications help you know when the incident lifecycle changes without continuously watching the dashboard.
Configure notifications