Monthly SLA reports

A monthly SLA report is a PDF that tells one client, in their own language, how their systems performed last month: uptime measured against the SLA target you set for them, incidents, response times, and how much of the month was actually measured. It's the document that turns a month of one-minute checks into something you can hand to a client — see What is an SLA? for the commitment it measures.

Who gets a report

Reports are a paid feature — the plans page shows which plans carry them. A workspace on a plan without reports doesn't generate them.

Within a paid workspace, a report is generated per client — but only for clients with something real to report on: at least one monitor attached to one of the client's sites, with checks actually recorded during the month. A client with no monitors, or whose monitors never ran that month, is skipped rather than handed an empty PDF. Internal monitors — the ones without a site — never appear in any client's report.

When reports run

UpAll generates reports automatically on the 1st of each month, at around 05:00 Riyadh time, covering the previous calendar month. There is nothing to schedule or trigger: if your workspace is on a paid plan when the run happens, the PDFs simply appear.

Where reports land — and how they reach the client

Finished reports land in the report archive in your console, and the archive is the delivery point. UpAll does not email reports to you or to your clients, and clients cannot see reports in their portal. Getting the PDF into the client's hands is a manual step: you download it and forward it yourself.

That's deliberate. The report carries your branding and your SLA commitment, and most MSPs want to read it before the client does — verify the numbers, prepare an explanation for a rough month — and then attach it to their own monthly service email. The archive shows each report's status and measurement coverage so that review takes seconds; Downloading reports walks through it.

What's inside

Each report opens with a summary block — uptime versus the client's SLA target, total checks, incidents, p95 response time, downtime minutes, and measurement coverage — followed by a per-system table, the month's incident log, and a timezone footnote. What's in a report explains every section.

Two rendering rules are worth knowing up front: the report is generated in the client's report language (not the interface language of whoever downloads it), and days are bucketed according to each monitor's timezone. Report language and timezone covers both.