Internet as a dependency: a node that can be needed, never judged down

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
bobbanandClaude Sonnet 5.5 committed 2026-10-30 23:14:24 +01:00
1 parent fca2dc0338
commit 7e625e7f42
11 files changed
+173 -22

No files matched your search

+1 -1
View File
@@ -454,7 +454,7 @@ each as a sentence. Narrow it by kind of change, by server, by how far back (a d
export. A server's Activity card links to its slice of it. Sign-ins and people's own data exports aren't changes and are left out. The raw audit log is the other tab of the same page (Change log → *Raw audit log*).
**Dependencies beyond servers** (Reference → Map → *Dependencies*, which draws the graph with the editor under it). Say that Gitea needs the server it is installed on, or that a server
needs Proxmox to answer. When what is needed is down, the alert of what needs it is folded under the first one exactly like a
needs Proxmox to answer. **Internet** is on the list too, as something a server, a service or a network device can need (a VPS, Hetzner, the router): it is drawn on the map and answers "what depends on Internet?", but nothing watches it, so it is never down and holds no alert back. It is only ever needed — it can't be made to need anything. When what is needed is down, the alert of what needs it is folded under the first one exactly like a
guest under its host — shown, labelled "caused by …", left out of notifications and tickets — and the root cause says what else it
takes down. It follows chains and the "runs on" links of servers; something needing two things is explained by whichever is down;
a loop explains nothing and one that would be made is refused. An integration is judged per kind of service (as its health is),