Reports
Every team gets a monthly report: an email on the 1st of each month and the same report as a PDF, ready to forward to a client. Every monitor also has its own PDF report for any period from 7 days to 12 months.
The monthly report
The report covers the previous calendar month for every monitor the team had during it. A monitor removed during the month is listed with the date it was removed and with what was measured before; one removed earlier is not part of the report, and a removed monitor gets no quality signals or actions.
- Summary: availability, confirmed incidents and recommended actions, with what changed and why it matters.
- Services: availability, downtime, median and 95th-percentile response time, certificate and domain expiry, and the state of each monitor at the end of the month, plus the mean response time of the last four months.
- Quality signals: the latest Lighthouse scores, Core Web Vitals, security headers, IP blacklists, broken links and DNS changes, where those checks are set up.
- Scheduled jobs and server agents, with their missed runs.
- Incidents: every incident open during the month, the longest one as a timeline (first failed check, detected, notified, first update, and how it ended), and a list of all of them. Each one says how it ended: recovered (a check passed again, with that check's time), closed by hand, or monitor removed. Removing a monitor closes its open incidents as "monitor removed", never as a recovery. An AI incident analysis you created for an incident is quoted with its date.
- Recommended actions: each one follows from a measurement in the report, such as a certificate that expires within 30 days or a failing check. The report says what to check, not who should do it.
- Scope & method: the reporting window and how each figure is measured.
Every figure comes from the stored results of your checks. Availability is the share of all check runs in the month that succeeded, every website's runs counted alike; runs during a scheduled maintenance window or during an incident archived as a false alarm are left out, run by run. Downtime is the time incidents were open within the month: one that began earlier counts from the start of the month, one still open until its end, one whose monitor was removed until the removal. Certificate and domain expiry is counted in days from the end of the month to the expiry date. "What changed" compares response times only across websites measured in both months. Response times come from successful checks only. Monitors show their hostname, never the full URL.
Download the PDF
- Go to Settings → Team → Email delivery, section Monthly Report.
- Under PDF report, pick a month: last month, any of the twelve before it, or the current month so far.
- Click Download PDF.
Every team member can download it; only admins can change the email settings. The same PDF is attached to the monthly email.
For any other stretch of time, use Report (PDF) at the top of the Monitors page: one report across all monitors for the last 7 days, 30 days, 90 days or 12 months, up to the last full hour. A reseller finds the same button on a managed team's monitor list; that report carries the reseller's branding.
Branding
The PDF carries your team's branding: its logo, its colours (the dark and accent tones are derived from your primary colour) and its name. If your team is managed by a reseller, the report carries the reseller's branding and nothing of Hoppla. When no logo is set, the name is printed instead.
AI-written summary
On Starter and above you can have the three summary texts of the PDF (the overview, what changed and why it matters) written with AI assistance. Switch on AI-written summary in the PDF in the monthly report settings.
- The AI only writes prose. It is given the figures of the report and asked to describe them without stating any number. Every text it returns is checked, and any text that contains a digit, a number word, a percentage, a link or formatting is dropped and replaced by the standard sentence. The figures in the PDF always come from your monitoring data.
- The PDF marks the summary as written with AI assistance.
- It is used in the report you download and in the automatic monthly email.
- The number of AI summaries per month depends on your plan (Starter 2, Pro 10). Downloading the same report again does not count again. When the monthly allowance is used up, the PDF uses the standard sentences.
The data sent for a summary is the team name, monitor and job names, hostnames (no paths), the report's figures, and incident titles and durations, with a pseudonymous team identifier. It goes to OpenRouter, which passes it on to a model provider. Incident update texts and your stored AI incident analyses are not sent.
The per-monitor PDF
Open a monitor and use Download report to get its PDF for 7 days, 30 days, 90 days or 12 months. It has the same layout, scoped to that monitor, and adds a day-by-day table (month by month for 12 months) of availability and mean response time.
API
| Report | Endpoint |
|---|---|
| Monthly report of your team | GET /api/v1/reports/monthly/pdf?month=YYYY-MM |
| Monthly report of a managed team (reseller) | GET /api/v1/reseller/managed-teams/{id}/reports/monthly/pdf?month=YYYY-MM |
| Monitor report | GET /api/v1/monitors/{id}/report/pdf?period=7d|30d|90d|12m |
month defaults to the previous month. The endpoints need the monitors:read scope and answer 503 with a Retry-After header when the PDF cannot be created right now.