Table of contents
How we store data
On this page
Every check we run generates a certain amount of data. We call these the “results”. Results are made up of various parts:
- Metadata like timestamps, response times, fail/success flags, run location etc.
- JSON or other response bodies, response headers, request timing data
- Playwright Test traces and videos
- Screenshot files
- Run logs with debug or
console.logstatements.
Data Retention
Depending on your plan we keep the results data according to the following retention policy:
| Hobby | Team | Enterprise | |
|---|---|---|---|
| Raw data retention | 7 | 30 | 180 |
| Aggregated data retention | 30 | 1 year | 25 months |
Simply put, you can “scroll back” within the defined period for raw data and inspect all the details of each result. After that, we store aggregates of the relevant statistics like average, p95 and p99 response time and success ratio.
We are continuously working on tweaking and improving our data retention policy. Expect updates.
Global locations & scheduling strategies
Last updated on August 27, 2024. You can contribute to this documentation by editing this page on Github