Add a weekly digest and report which version of the agent each server runs
- Weekly digest through the notification channels: alerts now, a week of uptime, what happened, disks heading for full, expiring secrets and domains, updates waiting, planned maintenance. Off until switched on in Settings -> Notifications; Preview and Send it now there. Setting key 'digest'. - Agents say their version in every report (Linux and Windows scripts are version 2); the server compares it with the scripts it serves and marks agents that are behind on the Servers, server and Updates pages. servers.agent_version, migration 0026. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
3da5c639b1
commit
aa94d84f6c
28 files changed
+3179
-19
No files matched your search
+16
-4
@@ -14,12 +14,24 @@ This page is about how to do that, safely, and how to tell it worked.
|
||||
| a version that only changed the app | No. Older agents keep working: a report is read the same way as before. |
|
||||
| the version that added **pending updates** (the Updates page) | Yes, to see updates. Until then the server's row says *not reported*. Everything else about it carries on as before. |
|
||||
|
||||
Each agent script carries a version number and sends it in every report; Homelab Manager compares it with the
|
||||
scripts it serves itself, so it can tell you which agents are behind. A change to an agent is only given a new
|
||||
number when it is worth installing the agent again for.
|
||||
|
||||
| Agent version | What it added |
|
||||
|---|---|
|
||||
| 1 | Everything before the number was reported — so an agent that says no version is version 1. |
|
||||
| 2 | Reports pending updates, and its own version. |
|
||||
|
||||
Reports are always read leniently — a field an older agent doesn't send is simply left alone, and a field
|
||||
an agent sends that the server doesn't know yet is ignored — so there is never a rush, and a mixed fleet of
|
||||
old and new agents is fine.
|
||||
|
||||
**How to tell which agents are old.** The agent doesn't report a version number. The visible sign is the
|
||||
**Updates** page showing *not reported* for a server that has an agent. On the machine itself:
|
||||
**How to tell which agents are old.** Homelab Manager says so: a server whose agent is behind shows an
|
||||
*agent behind* badge on the **Servers** page, *update available* beside **Agent** on its own page, and *behind* in the
|
||||
**Agent** column of the **Updates** page, which also counts them under *Agents to update*. (An agent that was
|
||||
updated before version numbers existed reads as "v1 or older" until it has been updated once more.) On the
|
||||
machine itself:
|
||||
|
||||
```bash
|
||||
# Linux — prints 1 or more if the script knows about updates, 0 if it doesn't
|
||||
@@ -122,8 +134,8 @@ playbook*) — a good way to try it on one machine first, then run it on the res
|
||||
|
||||
## Checking it worked
|
||||
|
||||
1. **The Updates page.** The server's row changes from *not reported* to its figures within one reporting
|
||||
interval (15 minutes by default; on Windows the installer reports straight away, and on Linux you can
|
||||
1. **The Updates page.** The server's row changes from *not reported* to its figures, and its **Agent** to the
|
||||
current version, within one reporting interval (15 minutes by default; on Windows the installer reports straight away, and on Linux you can
|
||||
start one now — below).
|
||||
2. **Last seen** on the server's page moves to *just now*.
|
||||
|
||||
|
||||
Reference in new issue
Block a user