Documentation
Complete guide to setting up website monitoring with PingZen. API documentation, code examples, and best practices.
SLA Reports
Every monitor can produce a self-contained SLA report on demand — a dated document you can attach to a client review, a postmortem, or a compliance folder. No scheduling and no setup: pick a period, pick a format, download.
Where to find it
The Download report button appears in two places:
- Monitor page — in the header, next to Edit / Check Now / Pause. The report period defaults to the time range you are currently viewing (24h / 7d / 30d).
- Monitors list — the download icon is the first action on each monitor, in both the card (grid) and the table (list) view.
Both open the same dialog: choose a period (Last 24 hours / 7 days / 30 days) and a format (PDF or CSV), then press Download.
What’s in the report
Each report is generated from the same data the monitor page shows, so the numbers can’t drift:
- Availability — uptime percentage and “nines” rating, total / successful / failed checks
- Reliability (ITIL) — MTTR (mean time to recovery), MTBF (mean time between failures), incident counts, total downtime
- Latency — P50 / P90 / P95 / P99, plus average, min, and max
- Error budget — when an SLO target is set, consumed vs. allowed downtime and remaining budget
- Incident history — start, duration, and the failure reason for each incident in the period
- Maintenance — time spent in announced maintenance windows is excluded from uptime, the industry-standard way
PDF or CSV?
- PDF — a formatted document for stakeholders: clean tables, ready to share or archive.
- CSV — the same metrics as raw rows for spreadsheets and data analysis. Values are sanitized against spreadsheet formula injection.
The downloaded file is named sla_report_<monitor>_<date>.pdf (or .csv).
Periods and data retention
Reports cover the last 24 hours, 7 days, or 30 days. Uptime is duration-weighted and survives for the full window. Raw per-check latency is kept for a shorter retention period, so latency percentiles are most complete on the 24h and 7d views.
Related
- Status page SLA reports — a public, account-free 90-day PDF that visitors of a status page can download themselves.
- Scheduled reports deliver the same SLA metrics to your inbox on a daily, weekly, or monthly cadence — use them when you want the report to arrive automatically instead of downloading it on demand.
Common Questions
What protocols can I monitor?
PingZen supports 23 protocols: HTTP/HTTPS, WebSocket (WS/WSS), TCP, UDP, ICMP Ping, gRPC, DNS, WHOIS, SSL certificates, Email (SMTP/IMAP/POP3), FTP/FTPS, DNSBL, PageSpeed, SOCKS5, MTProxy, API Check, and Transaction. You can monitor websites, APIs, servers, databases, and any network service.
How fast can I get alerts?
Telegram alerts are delivered within 1-2 seconds of detection. Slack and Discord notifications arrive almost instantly. You can configure multiple alert channels for redundancy.
Can I organize monitors by project?
Yes! PingZen supports workspaces, which let you organize monitors by project, environment, or team. Each workspace can have its own alert configurations and team members.
Is there an API for automation?
Absolutely. PingZen provides a full REST API with OpenAPI documentation. You can create, update, and delete monitors programmatically.
How do status pages work?
Status pages are public, branded pages showing your services' uptime. You can display real-time status and allow customers to subscribe for updates.
What happens if I reach my monitor limit?
We'll notify you when approaching your limit. You can pause some monitors or contact us for increased capacity. We never stop monitoring without warning, ensuring your critical services stay protected.
Ready to stop missing downtime?
Join thousands of teams who trust PingZen. Setup takes 30 seconds.