Reports
Reports summarise the state of the managed systems as a PDF: for customers (proof of service) or internally (what needs to be done). You find them under Automation > Reports.
The reports (since v3.74.0)
| Report | For | Content |
|---|---|---|
| Monthly report | Customer | Overall score (0-100) and a traffic light per area: backup, updates, security, availability, storage. Plain-language recommendations, systems outside the backup target, operating systems whose vendor support ends, incidents in the month, remote support sessions (QuickSupport and remote control with duration) and newly added systems |
| Backup proof | Customer | Per virtual system: last backup, age, agreed target (RPO), met yes/no with reason. Deliberately excluded systems with reason, backup storage (PBS) with usage and forecast |
| Updates & security | Customer | Update status per system (pending updates, security updates, end of support), firewall and Windows feature updates in the period, antivirus per Windows system, Mac security (FileVault, firewall, Gatekeeper), ACME certificates of the firewalls, vulnerabilities from security monitoring (Wazuh) |
| Inventory & changes | Customer | All systems with manufacturer, model, serial number, CPU, RAM, storage, operating system and site; overview of operating systems and device models; installed and removed programs and hardware changes in the period; software overview |
| Action items (internal) | Technicians | All open items per customer with finding and what to do: server offline, backup, backup storage full, unsupported operating system, security updates, pending reboot, antivirus, certificates, Mac settings, storage, critical checks. Without a customer across all customers |
| Audit trail (internal) | Administrators | User actions in the period |
Customer reports address the customer formally (German “Sie”) and contain no internal details. Customer accounts never see internal reports.
Rating
- Backup: same as the overview (backup SLA), state at the time the report is created. Green when all backed-up systems are within the backup target. Unreachable Proxmox hosts are named with a note (yellow); their VMs are missing from the list. The monthly report also lists the backup alerts in the period.
- Updates: “up to date” means no pending security updates and vendor support. Optional updates do not count. Red for operating systems without vendor support.
- End of support: vendor dates for Windows 10/11 (Home/Pro and Enterprise/Education per version), Windows Server 2008 to 2025, Debian 10 to 13 (including LTS) and Ubuntu LTS. Yellow from 180 days before the end.
- Availability: from the offline alerts of servers. Workstations do not count. Resolved alerts are kept for 60 days. If the period lies further back, the report shows a note instead of an availability figure.
- Antivirus: “active” out of all Windows systems. Systems without antivirus data count too (“no data”).
- Times: month and day boundaries and all times in the report are German local time (Europe/Berlin).
If a data source fails while creating a report, no report is created (error message). An automatic monthly report then shows as “failed” under Approval, is never sent and is recreated every hour.
- Overall score: average of the areas with data (green 100, yellow 60, red 20).
Creating a report
- Automation > Reports, tab Reports, button Create report, or click a template in the Templates tab.
- Choose the customer, optionally a site (only systems of that site).
- Period: empty = last month. Buttons for last month, 7/30/90 days and this year.
- Create report. The report then appears in the Reports tab (preview, PDF, HTML, e-mail).
Batch generation creates one report per selected customer or for all customers.
Sending the monthly report to the customer automatically
In the customer (Administration > Customers > customer > Edit > Monthly report):
| Field | Meaning |
|---|---|
| Report e-mail | One or more addresses separated by commas (max. 10) |
| Send monthly report automatically | Opt-in. Without it nothing is ever sent |
| Approve before sending | On by default. The report then waits under Reports > Approval |
How it works:
- In the first 7 days of each month from 6 am, every opted-in customer gets the monthly report about the previous month, exactly once per customer and month. If you opt in mid-month, the first report comes at the start of the next month. If Control was not running during the first 7 days, the report is caught up later in the month (for customers who already received the previous month's report).
- With approval: the report appears under Approval and the tab shows the count. There: preview, PDF, Approve and send (one or all), Discard. A report still waiting after 3 days triggers a reminder via the notification channels that selected the event Monthly reports awaiting approval (or have no event filter).
- The customer monthly report does not name technicians.
- Without approval: the report is sent right away.
- The e-mail contains a short cover text and the report as a PDF. Failed sends stay under Approval with the error and can be sent again.
Requirement
Sending needs SMTP under Settings > Notifications.
Cover text: setting report_mail_text (placeholders {monat} = month, {kunde} = customer, {firma} = company). report_mail_sender_name sets the company name in the text, otherwise the company name from branding is used.
Schedules
Under Schedules any template can be generated regularly (daily, weekly, monthly, cron), e.g. the action items every Monday. Schedules only create reports; sending is manual or through the automatic monthly report.
Customising templates
System templates (lock icon) receive improvements with every update as long as nobody edited them. To customise one, better copy it and edit the copy.
The system templates up to v3.73 are now called “… (veraltet)” (outdated). They keep working and can be deleted once no longer needed.
Data sources
Templates get their data through data_queries. An entry with provider returns prepared data:
[{"name": "backup", "provider": "backup"}, {"name": "meta", "provider": "meta"}]| Source | Content |
|---|---|
meta | Customer, customer number, site, period, number of systems per kind |
hosts | All systems in scope (module, kind, OS, online, maintenance) |
summary | Traffic lights per area, overall score, recommendations |
backup | Backup SLA per VM, exclusions, PBS storage |
patches | Update status, end of support, firewall update runs, feature updates |
security | Antivirus, Mac security, ACME certificates, Wazuh |
alerts | Alerts in the period, server availability |
capacity | Storage running out (forecast) |
inventory | Hardware per system, software overview |
changes | Software/hardware changes, new systems |
support | QuickSupport and remote control sessions |
checks | Failing checks |
actions | Action items (internal) |
Direct queries on host tables ({"name": "x", "model": "windows_server"}) still work.
All sources respect customer, site, host group and period from the create dialog as well as the user's module rights.
Template helpers
format_date, format_datetime, format_bytes, de_number, de_percent, duration (minutes), bar (bar for percentages), sev_class and sev_label (traffic light colour and text), yesno.
Layout
The Modern (Hochformat) layout (base templates) provides a header band with logo and company name from branding, customer and period, page numbers and the CSS classes kpis, pill, box and empty.
Permissions
- Create, approve, send, templates:
reports.manage - View:
reports.view - Customer accounts only see reports of their own customer, never drafts awaiting approval and never internal reports.
- The automatic monthly report sees all modules of the customer.