Detailed Logs shows the individual availability checks behind a monitor's charts, availability percentage, and incident decisions. Use it when a website fails intermittently, returns an unexpected status code, or has a response-time spike.
Open Detailed Logs
- Open Monitors from the customer dashboard.
- Select the monitor you want to investigate.
- Open Monitor Tools and select Detailed Logs.
- Select Open detailed logs.
The page opens with the last 24 hours selected and 100 rows per page.
Understand each row
| Column | Meaning |
|---|---|
| Time | When the scheduled check was recorded, shown using the dashboard time-zone preference |
| Status | Up for a successful check result or Down for a failed check result |
| HTTP | HTTP response code, when the request reached an HTTP server |
| Latency | Time used by that availability request |
| Diagnosis | Normalized category such as timeout, DNS, SSL/TLS, blocked, rate limited, or server error |
| Confirmation | Regional confirmation decision when the primary check failed |
| Error | Short request error, when available |
| URL | Monitored URL associated with the check |
A Down row is an individual failed check. It does not necessarily mean the monitor's confirmed status changed to Down or that an incident opened.
Choose a range
The preset ranges are:
- Last 24 hours.
- Last 7 days.
- Last 30 days.
- Custom.
Raw check logs are retained for 30 days, so one custom query cannot exceed 30 days. Use Monitor Details rollups for older one-month or one-year availability and response-time summaries.
Changing a range or filter does not replace the current result set immediately. Select Apply when the choices are ready. This lets you edit several fields without making the table unusable between changes.
Filter the results
You can combine:
- Status: All, Up only, or Down only.
- Diagnosis category.
- Exact HTTP status code.
- Text contained in the error.
- Minimum response latency.
- Maximum response latency.
- From and To timestamps.
Select Reset to return to the last 24 hours, all statuses, no diagnosis or latency filters, and 100 rows per page.
Read the summary cards
The cards above the filters summarize the full filtered result set, not only the visible page:
- Matching rows.
- Up checks.
- Down checks.
- Average latency.
- Slowest latency.
This is why selecting Down only can show more matching failures than fit on one page.
Navigate and sort
Choose 50, 100, 250, or 500 rows per page. Pagination controls appear above and below the table, and numbered shortcuts let you jump through a large result set.
Select a sortable column heading to change the order of the rows currently displayed on that page. Time starts newest first. Filtering and page counts are calculated across the full selected range; header sorting is a current-page display operation.
Export matching checks
Select Export CSV to download the full filtered result set in batches. The file includes timestamps, status, HTTP code, latency, diagnosis, confirmation summary, failure reason, recommended action, error, and URL.
Exports are limited to 50,000 matching rows. Narrow the range or add filters when a result exceeds that limit. The export uses the applied filters, not unsubmitted changes still visible in the form.
Protect sensitive information
Detailed Logs does not return saved authorization values, Basic Authentication passwords, or custom-header secrets. Do not put credentials into URLs, monitor names, or other fields intended for display and export.
When sharing a CSV with Support or another person, review its URLs and error details first. Remove customer identifiers or internal endpoint paths that the recipient does not need.
If no checks appear
- Confirm the monitor is active rather than paused or archived.
- Wait at least one configured interval after creating or activating it.
- Select Reset in case a filter excludes the available rows.
- Verify the selected range is within the 30-day retention period.
- Return to Monitor Details and review Failure Diagnosis.
Contact Support with the monitor name, URL, selected range, and approximate missing-check time if an active monitor continues to have no logs. Never include passwords, verification codes, or full authorization-header values.