Documentation
Monthly Reports
Export a self-contained HTML file summarizing customer infrastructure status for the month.
An agency charges to monitor infrastructure, and each month the customer wants to see “what did you do”. All the data needed to answer that has already been collected — this feature turns it into a page the customer can read.
Creating a Report
Choose project → Reports → choose month (YYYY-MM) → Preview.
The preview is the final document. If you like it, press Save and choose where
to write the .html file.
Content
One summary line per VM:
| Column | Meaning |
|---|---|
| Days with data | How many days in the month actually had samples |
| Sample count | Total successful poll attempts |
| Avg/peak CPU | Weighted average by samples per day |
| Avg/peak RAM | As percentage |
| Highest disk | Percentage of the fullest mount |
| Disk change | Percentage point increase (or decrease) of the fullest mount during the month |
| Events | Count of critical, warning, and connection-loss events |
Notable events, most recent first — this section is usually what the customer reads most carefully.
Average is computed weighted by sample count per day: a day with only four polls is not counted equal to a full day.
Why Reports Read from Aggregated Data
Raw samples are kept only 14 days. If reports read from them, a “monthly report” would silently contain only half a month and still call itself a monthly report.
So it reads from the daily aggregate table, recorded continuously and kept long-term. Events are read directly, since they are not cleaned up.
Consequence to know: any month you haven’t enabled monitoring, that month has no data. Reports cannot reconstruct the past.
File Format
Output is one self-contained HTML file:
- no scripts,
- no external fonts,
- no linked images,
- no network calls when opened.
Meaning you can email it, archive it, and open it again three years later with the same appearance. Need PDF? Open in a browser and print to PDF — the layout is already made to fit pages.
Suggested Workflow
- Set a regular schedule, e.g., the 1st of each month.
- Export the report for each of your projects for the completed month.
- Skim the notable events section before sending — this is where you add value: one line explaining “the incident on the 14th was provider maintenance, handled” is worth more than a whole page of numbers.
- Send by email, or print to PDF if the customer needs a signed copy.
Current Limitations
- Reports are per project, no merged view across multiple projects.
- Cannot yet customize logo or brand colors.
- No automatic export schedule — still manual button presses.
These are on the next development roadmap.