Purpose
Reports help agencies and teams show what happened during a month. They are meant to be readable by clients and stakeholders, not only by engineers.
Included monitoring data
Monthly web report uptime metrics focus on enabled web monitors, especially Uptime and Keyword checks. Other monitor types such as TLS, Domain, Heartbeat, and Sitemap can appear as operational context where supported.
Report sections
- Summary metrics such as average uptime, incident count, downtime, and longest incident.
- Incident timeline with resolved and ongoing incidents.
- Availability and trend information where enough data exists.
- Methodology notes so customers understand what is measured.
- Links to the signed-in Watchfox app export flow for detailed CSV data.
Branding and targets
Report branding and optional uptime targets depend on project and plan configuration. Targets are reporting targets, not automatic legal SLA guarantees.
CSV exports
Monthly PDF reports link to the signed-in Watchfox app export flow instead of raw API CSV endpoints. If you are not signed in, Watchfox asks you to sign in and then returns you to the report export context.
Available app export buttons are Report summary CSV, Incidents CSV, and Monitor checks CSV.
Raw monitor checks are retained only for recent troubleshooting. Free workspaces keep a shorter raw history than paid plans; paid plans keep the standard recent raw window. For older report periods, monitor-check CSV output may be empty or limited by retention; report summary, rollups, daily summaries, and incidents are the safer long-term reporting sources.
API users can still call CSV export endpoints directly with a project API key or a Bearer session plus project_id where supported.
Troubleshooting reports
If a report looks unexpected, check the selected month, project, enabled monitor set, maintenance windows, and whether recent incidents were still open at the time the report was generated.