Rename the Monthly report menu entry to Reports

The page also gives quarterly and annual reports. The route is unchanged; the
scheduled monthly message in Notifications keeps its name.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
bobbanandClaude Sonnet 5.5 committed 2026-11-08 22:26:03 +01:00
1 parent 587e8856a0
commit 4a7b1494c8
5 files changed
+6 -6

No files matched your search

+1 -1
View File
@@ -188,7 +188,7 @@ A scheduled backup of the app's own database that fails sends one message throug
| "Homelab monthly report — <month>" | On the chosen day of the month (1–28) and time, in the notification time zone, **only if switched on** under Settings → Notifications. One plain-text message through every channel that is on, about the month just over; quiet hours hold it like any other notification. |
Availability of servers and endpoints, incidents (how many, how long they took, the longest), updates and patch plan runs, restore tests and the state of the backups, and what was renewed — a topic only where there
is something to say, now with a **Service levels** topic (how each target did against its error budget). The same report is on the Monthly report page. *Preview last month* and *Send last month now* are on the settings page.
is something to say, now with a **Service levels** topic (how each target did against its error budget). The same report is on the Reports page. *Preview last month* and *Send last month now* are on the settings page.
With **Also send a quarterly report** on, "Homelab quarterly report — Q3 2026" follows the monthly one after the month that ends a quarter (March, June, September, December), and with **Also send an annual report** on, "Homelab annual report — 2026" follows
the December one. Both are the same report over three or twelve months, sent the same way; both are off until switched on.
+1 -1
View File
@@ -782,7 +782,7 @@ coming back, to the minute), and is measured over calendar months in the notific
pace so far would end the month), and how each of the last six months went. When **80 %** of the budget is used it is a warning, and when it is overspent a critical alert, until the month turns over — switchable per target. Planned maintenance is
**not** taken out: down is down. A target with nothing recorded for the period says so rather than guessing. `/metrics` has the target, the figure and the minutes left; administrators set targets, everyone sees them.
**Monthly, quarterly and annual reports** (Records → Monthly report; and, if switched on, a message on a day of the month). How a calendar month went, on one page that can be read, printed and copied as text:
**Monthly, quarterly and annual reports** (Records → Reports; and, if switched on, a message on a day of the month). How a calendar month went, on one page that can be read, printed and copied as text:
**availability** (servers, from when each stopped reporting and reported again; endpoints, from every check's answers, kept day by day for years; integrations), **incidents** (how many began and
ended, how long they took, the longest, by kind, and which are still open), **updates** (update runs and patch plan runs, how many updates were installed, by server), **restore tests** recorded in the
month and the **backups as they are now**, and what was **renewed** (a certificate or a domain whose expiry moved clearly later — noticed when the app re-reads the date). The month is on the clock of the notification time zone;
+2 -2
View File
@@ -74,7 +74,7 @@ page's own top-level link.
| To do | `/todo` | ✅ | ✅ | ✅ |
| osTicket | `/osticket` | ✅ | ✅ | ✅ |
| **Records** | | | | |
| Monthly report (and quarterly, annual) | `/reports` | ✅ | ✅ | ✅ |
| Reports (monthly, quarterly, annual) | `/reports` | ✅ | ✅ | ✅ |
| Costs | `/costs` | ✅ | ✅ | ✅ |
| Change log (and the raw audit log, `?view=audit`) | `/changes` | ❌ | ✅ | ✅ |
| **Reference** | | | | |
@@ -184,7 +184,7 @@ even further, to admin only:
- **Backup coverage** is a read-only page for everyone. On **Updates**, everyone sees what is waiting and how update runs
are going; starting an update run (**Update…**) or stopping one needs operator.
- **Patch plans** (Updates → Patch plans) can be seen by everyone, with how they went; making, changing, switching off and removing one needs administrator (it will run on its own, at night);
**Run now** and **Stop** need operator, like an update run. The **Monthly report** page is for everyone signed in; sending it now, and its schedule (Settings), are administrators'.
**Run now** and **Stop** need operator, like an update run. The **Reports** page is for everyone signed in; sending it now, and its schedule (Settings), are administrators'.
**Mark as expected** on a server's Ports card, and on the Ports page under Network (one port, or **Mark all as expected**), which ends a new-port alert, needs operator, like any note on a port; everyone signed in sees which ports are *New*.
- **Acknowledging an alert, handing it over, and taking it back** need operator (the person it is handed to must be an operator or
administrator); everyone sees who has what. **Incidents** (Alerts → History) are readable by everyone signed in; writing a note needs operator, and a note
+1 -1
View File
@@ -193,7 +193,7 @@ export const NAV: NavEntry[] = [
label: "Records",
icon: <IconHistory size={20} />,
items: [
{ to: "/reports", label: "Monthly report", icon: <IconReportAnalytics size={20} /> },
{ to: "/reports", label: "Reports", icon: <IconReportAnalytics size={20} /> },
{ to: "/costs", label: "Costs", icon: <IconCoin size={20} /> },
{ to: "/changes", label: "Change log", icon: <IconGitCommit size={20} />, minRole: "operator" },
],
@@ -1218,7 +1218,7 @@ export default function NotificationSettings() {
<div className="card-body">
<p className="text-secondary">
One message a month with last month in numbers: how available the servers and endpoints were, the incidents and how long they took, updates applied (by hand and by patch plans),
restore tests, and what was renewed. The same report is on the <a href="/reports">Monthly report</a> page, to read and print. Quiet hours hold it like any other notification.
restore tests, and what was renewed. The same report is on the <a href="/reports">Reports</a> page, to read and print. Quiet hours hold it like any other notification.
</p>
<label className="form-check mb-3">
<input type="checkbox" className="form-check-input" checked={monthly.enabled} onChange={(e) => setMonthly((m) => ({ ...m, enabled: e.target.checked }))} />