Monitor logs
Inspect the details of every check Hyperping performs on your monitors.
Monitor logs give you a ping-by-ping record of each check, including response status codes, response times, and the region the check ran from. You can access logs from any monitor's report page by navigating to the /logs tab.
Logs are useful when:
- You need to investigate a false positive and see what Hyperping actually received
- You want to compare response times across different regions
- You are debugging intermittent errors or slow responses
- You need to verify that a fix or deployment resolved an issue
The logs view shows each check with its status code, response time, and region.
Access logs
- Open the Hyperping dashboard and click on a monitor.
- Navigate to the Logs tab on the monitor's report page.
What logs capture
| Field | Description |
|---|---|
| Status code | The HTTP status code returned by the endpoint |
| Response time | Time in milliseconds from request to response |
| Location | The datacenter region that performed the check |
| Method | The HTTP method used for the request |
| Timestamp | When the check was performed |
Use cases
Debugging false positives: If a monitor triggered an alert but your service seemed fine, check the logs to see what status code and headers Hyperping received. This often reveals issues like rate limiting, firewall blocks, or CDN errors that only affect external checks.
Verifying monitor behavior: After changing a monitor's configuration (expected status code, regions, or assertions), use logs to confirm the checks are returning what you expect.
Tracking regional performance: Compare response times across different regions to identify latency issues. If checks from one region consistently show higher response times, it could indicate a routing or infrastructure problem in that area.
Troubleshooting
Logs show a different status code than expected.
Your endpoint may be returning redirects (301/302) or your server could be rate limiting Hyperping's requests. Check the response headers for Location or rate limit headers.
Response times vary widely between regions.
This is normal if your server is located in a specific region. Checks from nearby datacenters will be faster. Consider adjusting your selected regions to match where your users are.
I do not see logs for a monitor.
Logs are generated with each check. If the monitor was just created, wait for the first check interval to pass. If the monitor is paused, no new logs will be generated.
