Add homelab_server_boot_time_seconds to /metrics

When each agent-reported server last started (last report minus uptime), so
uptime is time() - the metric and a reboot shows as it moving.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
bobbanandClaude Sonnet 5.5 committed 2026-11-08 21:56:38 +01:00
1 parent 41fbbf3467
commit 48aea747bc
3 files changed
+8

No files matched your search

+1
View File
@@ -259,6 +259,7 @@ All gauges. The same table is checked by a test against what `/metrics` really s
| `homelab_info` | `environment` | Always 1; says which installation this is. |
| `homelab_server_up` | `server` | 1 if the agent has reported within the offline threshold (Settings → Notifications, or the server's own limit if it has one), else 0. Servers that never reported are left out. |
| `homelab_server_last_seen_timestamp_seconds` | `server` | When the agent last reported. |
| `homelab_server_boot_time_seconds` | `server` | When the server last started, as a Unix time, worked out from the uptime its agent reports (Linux agent 8, Windows agent 7 and later). How long it has been up is `time() - homelab_server_boot_time_seconds`; the value only moves when the server reboots. |
| `homelab_server_cpu_load_percent` | `server` | CPU load as the agent reports it. |
| `homelab_server_memory_used_percent` | `server` | Memory in use. |
| `homelab_server_disk_used_percent` | `server`, `mount` | How full each disk is. |