Agent diagnostics ("what the agent couldn't collect") and services to ignore per server
- Agents (Linux 6, Windows 5) note each check they couldn't make and why; the server page turns that into tips and fixes, including when the agent is behind - Linux --prepare leaves its notes for the report; a missing prepare step is itself noted - Services to ignore are set per server from the Host health card (names or * patterns), applied on the server so alerts and /metrics drop them at once; saving alert limits keeps the list Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
b5384c1e03
commit
c3bc6bbf72
26 files changed
+4118
-45
No files matched your search
@@ -572,7 +572,9 @@ Proxmox guest) how old its backup may be — and per disk, either a limit or "no
|
||||
for this disk". Whatever is left empty follows Settings, so changing the global limit
|
||||
still reaches every server that hasn't said otherwise. They apply everywhere the global
|
||||
ones did: the alerts, the notifications, the dashboard, the map, the forecast, the
|
||||
digest and `/metrics`.
|
||||
digest and `/metrics`. The same place keeps the **services to ignore** on that server — an updater that always shows as failed, say — which can also be set from its
|
||||
Host health card; and a card, **What the agent couldn't collect**, tells you why a figure is missing (no `smartctl`, an update check that didn't answer …) and what
|
||||
to do. See AGENT_UPDATE.md.
|
||||
|
||||
**Inventory** (Infrastructure → Inventory) keeps the hardware behind it all: name and
|
||||
kind, maker, model, serial, where it sits (and rack unit), when it was bought and for
|
||||
|
||||
Reference in new issue
Block a user