For an Authentik that is not in use at the moment: "Do not alert about certificates" on the integration stops the certificate alerts (and clears the ones raised) while the page still lists the certificates and /metrics still carries their expiry. Outposts, tokens, failed sign-ins and configuration errors are unaffected. Same pattern as Fragnet's mute boxes. Tests and docs added.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A failed service now raises an alert (and counts in /metrics and the public API) only when the server is told to watch it, by name or pattern, or * for all. Failed services that are not watched still show on the Host health card with a Watch button. Replaces the ignore list.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
About 1,600 more headings, buttons, table columns, status words, placeholders and short messages are translated. Tables of words built when the app loads are now read when they are drawn, so they follow the language, and a test fails if text is translated at load time.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Sent for every Fragnet game server seen turned on or off, whatever the notification switch says, with the server, game, account and, when a power signal sent from here caused it, which signal and who sent it.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A job whose last three runs in a row all finished with warnings is flagged and
raises an alert (on by default, switchable off per job). The size of the
destination, and its quota where the storage says, are read from the reports
and kept with each run; the Stored column shows the growth and, where the room
is known, when it will be full, with an alert inside the disk-forecast window.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A small translation system (the English text is its own key, so anything
without a Swedish entry stays English) and a Language switch in the user menu,
saved on the account (users.language) and following the browser when no choice
has been made. Swedish covers the menu, shared parts (search, tables, dialogs,
relative times), the sign-in page and the everyday pages: Dashboard, Alerts,
Servers, Updates, Maintenance, My work, Coming up, To do, Integrations and the
display settings. Server-written messages stay English for now.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
An axe-core check of 37 pages in both themes found and fixed low-contrast text
in the status colours (light) and tabs, pills and the info alert (dark),
in-sentence links with no underline, link targets under 24 px, selects with no
name and map nodes whose name did not start with their text. docs/ACCESSIBILITY.md
says what was found and how to run the check again.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Each change a read of a Fragnet account sees, and each power signal sent from
here with who sent it, is written down (180 days). A server's details show the
share of the last 30 days it was on, starts and stops, a seven-day bar and the
latest changes, with who asked for them.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A read of a Fragnet account that shows a server on (running or starting) after
it was off, or off (stopped or stopping) after it was on, sends one message
through the configured channels and routing rules, a line for each server.
A server first seen, one whose state is unknown and one being installed or
moved say nothing. Switch: Settings -> Notifications -> What to send (on by
default).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Each machine's card shows whether the last report was a backup, another
operation that was set aside, or one that could not be read (with the reason),
and counts of each since it was added. Administrators can see the start of an
unreadable report.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The first twenty warning messages of each run are kept with the run and shown
on the job and in its history. A job can be set to raise a warning-level alert
when its last run finished with warnings (off by default; a muted job raises
nothing; maintenance on the machine's server silences it).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Reads /api/admin/cluster/state (Technitium 14+): a Cluster table on the page,
alerts for a node unreachable for ten minutes (primary critical) and for a
secondary that has stopped taking the primary's configuration, and three
/metrics series. A server in no cluster shows nothing; a token that may not
view administration is told so and the rest of the read is unaffected.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Three tick boxes on the Fragnet integration: do not alert about disk space,
memory or backups. The page still shows the figures (a switched-off bar is blue
and the backups tile says not judged); /metrics is unchanged.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
One tile per server, time() - homelab_server_boot_time_seconds, in the Servers
row and following the Server picker.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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>
Operators can ask the game panel for a backup of a server whose plan has room for backups (Back up on the row, Back up now beside its backups). The panel makes it in the background; the page re-reads every 20 s until it is done. Refused here for a plan with no room, a suspended server, one already being backed up, or the same server within 30 s; the panel's own refusals (plan full, rate limit, permission) are shown in its words. Written to the audit log.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Both send to one fixed address each (api.telegram.org, api.pushover.net), take part in routing rules and the channel count, have a Send test that shows the service's own refusal, and keep their tokens and keys encrypted and out of errors and the audit log. A Telegram message carries one button, and a Pushover message one link, to the page where an alert can be acknowledged, silenced or snoozed.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Read every 15 minutes (Robot allows 200 requests an hour; read-only): each server's product, addresses, status, rescue system and paid-until, and the storage boxes. Adapter, sync service, hetzner_robot_state table, /api/hetzner-robot, Infrastructure → Hetzner Robot page, metrics and docs.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Each client is read every five minutes (read-only; qBittorrent's sign-in is the only POST): speed, queue and item states, network connection or paused queue, free space, SABnzbd's failures and warnings. Shared adapter, sync service, download_state table, /api/downloads, metrics and docs.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A New badge, a notice with Show only new and Mark all as expected, and Mark as expected on each row. Uses the same rule as the alert and the server's Ports card.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Alert settings keeps Alert rules, Service levels and Alert tickets; administrators get a link to Settings -> Notifications.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Old addresses (/alert-rules, /service-levels, /settings/notifications) lead to the right tab.
Notifications and Alert tickets stay administrator-only.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
README and INTEGRATIONS: what it reads, the config and token (15.0 or later),
the DNS test, the alerts and metrics, that its API has no CPU, memory or disk
figures, and how it differs from the Technitium DNS provider. ROLES: the page.
DATABASE: technitium_state, migrations to 0081, 91 tables. MONITORING: the
five alerts. PROMETHEUS-GRAFANA: the homelab_technitium_* metrics.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Apps → Authentik now has two tabs for administrators: Status (the outposts,
certificates, tokens and alerts, as before) and Users and groups (New user,
Users and Groups). The tab is a ?view=users link like the other pages' tabs;
everyone else sees only the status. Docs updated to name the tab.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
An administrator can make a user (user name, name, optional email, groups)
and gets a recovery link to send them, so they choose their own password;
no password is set or seen here. Uses a separate optional "Token for making
users" on the Authentik integration; reading never uses it, and it can be
removed again from the page. The link is shown once and never stored or
audited; the audit log records who made which user and link.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The health pass keeps the host ports Dockhand says running containers
publish (new table server_container_ports, migration 0080), matched to a
server by its Docker host's name. They name the port on the server's Ports
card and the network Ports table, ahead of a port preset and behind a
label somebody wrote, and in the new-port alert ("8096/tcp jellyfin
(container)"). Never written onto port notes, so a container's port is
still a new port; an unreadable host keeps its names, a day-old name is
dropped. Dockhand is now read on the health pass even with container
alerts off.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Lidarr and Readarr join the shared *arr reader. Integrations get an Inspect button that
runs the reader once and shows what each request returned as shapes (never values) and
where the result is empty. Operations -> App versions compares each application's version
with its newest GitHub release (lookup off until an admin switches it on; optional alert).
The Alerts page can group by source, kind of problem or type of alert. The shared HTTP
helper no longer reuses connections (stale-socket resets). Migration 0078; docs and tests
included.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
New integration kinds adguard (status, statistics, filter lists and a real DNS question
over UDP; alerts for DNS down/not running, protection left off, stale lists) and grafana
(alert rules firing or failing, data-source health). Optional warning for running Docker
images built more than N days ago (off by default). A server's overview cards can be
folded and arranged, kept per user. Migrations 0075-0077; docs, metrics and tests included.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A "What to do" note (text and/or link) can be written once for a whole kind of alert and
shows beside every alert of that kind; alerts now carry their kind and source type.
New optional setting: warn when a Docker host has N or more high vulnerabilities (off by
default). The wall display gains tiles (Hetzner and game servers running, critical
vulnerabilities, stuck downloads) and a summary line for each group of integrations,
also in share links. Migration 0074; docs and tests included.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
New integration kinds sonarr, radarr and prowlarr (shared adapter and sync, page under
Apps -> Media managers): own health findings, stuck downloads, nearly full disks.
Hetzner now reads load balancers (target health), floating IPs and certificates, includes
them in the cost estimate, and forecasts the month's traffic against the quota.
Migrations 0072 and 0073; docs, metrics and tests included.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
New integration kind "fragnet" reading Fragnet's Pterodactyl-based panel through the
client API (account key). Game servers page under Infrastructure with game, IP:port,
state, memory/disk, backups, schedules and databases; alerts for late backups and
nearly full disk/memory; operators can start/stop/restart/kill (audited). Metrics,
docs and tests included; migration 0071 adds fragnet_state.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
- Speedtest Tracker integration: charts, alerts for a slow line (median of the
last three tests under a share of what is paid for) and for failing tests.
- Costs page (Records): things paid for by hand plus Hetzner's estimate, totals
per currency, bills rolled forward into Coming up as Renewals.
- Status pages: a "Having trouble" state for things that answer but have an open
alert; Speedtest reads as the internet.
- Integrations page and kind picker grouped like the sidebar (one shared types
file); Notifications "What to send" shown one group at a time; Dashboard
integration sections follow the menu groups, with tiles for integrations that
have no widget.
- Docs, tests, and ROLES.md menu table brought up to date.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Closing several alerts together can now also close their osTicket tickets
(one by one, each written on its incident and in the audit log; one that
fails does not stop the rest; Undo does not reopen tickets). The single
and bulk close share one helper. Alerts moves to the top of the sidebar,
and Monthly report and Change log move to a new Records group. Docs updated.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
New Apps group (Home Assistant, Jellyfin, Immich, Paperless, Nextcloud,
Authentik). Hetzner Cloud moves to Infrastructure, NetBox to Network and
n8n to Automation. Docs now name the new locations.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
One integration per project (read-only API token, read every 5 minutes).
Alerts for a server that was running and is off, stuck statuses, traffic
at 80%/100% of the monthly quota, rescue mode left on, and late backups.
The Hetzner page lists servers, volumes, snapshots and a cost estimate; a
server the app knows by its agent gets a Hetzner card on its own page.
/metrics and docs updated.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Reads what Dockhand's scans have already stored (never starts one) every
15 minutes and raises a warning per Docker host with critical findings.
Unknown counts and stale readings are held, not treated as clean.
Settings -> Notifications has a switch (on by default); the Docker page
shows counts, scan coverage and the critical findings; /metrics and docs
updated.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Nextcloud: its own "Cron last run" setup check (GET /settings/setupcheck,
Nextcloud 28+, found by class name) raises an alert when background jobs have
stopped; other checks that report an error are one alert, warnings are shown
on the page. The core version Nextcloud says is available is shown too. Before
28, cron and the checks are unknown, never "fine".
Alerts page: bulk Close... (one reason, written on each incident, undoable) and
Open again. Bulk Wake now leaves closed alerts alone.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Close... on the Alerts page hides an alert with no end, with an optional reason
that is also written on its incident. It opens again only if it gets more
serious than when it was closed (said once) or the problem has been gone for
half an hour; Open again brings it back at once.
Built on the snooze table (kind, severity and note columns), so everything that
holds back snoozed alerts holds back closed ones. Audit log, change log and
/api/v1 alerts carry it.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Three read-only integrations, each with a monitoring page, alerts, maintenance
silencing and held-when-unreadable handling.
Nextcloud: database needing upgrade (critical), maintenance mode, and the data
disk running low; users, files and app updates with an admin app password.
NetBox: no background worker running, counts, and a list of the servers this
app manages that have no address in NetBox (a list, not an alert).
n8n: an active workflow whose last run failed, clearing when it next succeeds.
Disk messages for Immich, Paperless and Nextcloud now use the same units as
the pages that show them.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Bulk snooze: Snooze... and Wake on the ticked alerts, with undo that puts back
each alert's earlier snooze exactly.
Alert rules are judged for a server right after its agent reports, instead of at
the next 15-minute pass; only that server's rule findings change, and the check
is serialized with the pass so neither overwrites the other's state.
Photos on server and device notes: up to 12 each, shrunk in the browser,
accepted by their own bytes (JPEG/PNG/GIF/WebP, 4 MB), kept in the database and
removed with the server or device.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Three read-only integrations, each with a monitoring page, alerts, maintenance
silencing and held-when-unreadable handling.
Prometheus: scrape targets that stop answering (5 minutes, one alert per job)
and alerts that Prometheus's own rules fire (critical when labelled so).
Immich: disk under the library filling, failed background jobs, counts.
Paperless-ngx: worker/database/Redis in error, documents that failed to
import, index and sanity check, disk. Immich and Paperless also in /metrics.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
New Authentik integration (read-only, every 5 minutes): version, workers,
outposts and their health, certificates and API tokens that expire, failed
sign-ins and configuration errors. Monitoring -> Authentik page.
Alerts: an outpost that serves apps has gone quiet (critical), certificate or
token about to run out (critical close to it), no worker, failed sign-ins,
configuration errors. Held by maintenance, held when unreadable, in /metrics.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
New Jellyfin integration (read-only, every 2 minutes): version, restart wanted,
streams and transcoding, failed scheduled tasks, item counts, failed sign-ins.
Monitoring -> Jellyfin page with a peak-streams history, three alerts, /metrics.
When Jellyfin runs on a managed server, an update run asks first if people are
streaming (409 "watching" unless startAnyway), and a patch plan waits up to two
hours for them before updating that server.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Duplicati reports each operation to a secret address (its own send-http-url option), so
nothing calls Duplicati and no password for it is kept. Each machine is a source; each job
is learned by name and shows its last result, duration, size, changes and a history.
A failed run is a warning (critical from the second in a row); one that has not succeeded
for longer than expected (per job, 2 days by default) is a warning, critical at three
times that. Maintenance on the machine's server silences them; /metrics series added.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
With Dockhand connected, an image the app recognises (about 20 with a health endpoint of
their own, plus a few dozen web UIs) is offered as an endpoint check on that app's own
health address, with what a good answer looks like set up as a value check: Immich's ping
says pong, Nextcloud's status.php is not in maintenance, Gitea's health says pass, and so
on. Asked on the Docker host's address at the port the container publishes. Container
ports are now read from Dockhand's list.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
From Dockhand, on the health pass: a container that keeps restarting (critical, with
its exit code), one whose own health check fails, one that stopped unexpectedly, one
created and never started for an hour, and a Docker host Dockhand cannot reach. A stop
is only news when it was seen happen, so stacks switched off long ago stay quiet.
A Leave alone button on the Docker page and a list in Settings; on by default.
Also fixes a date-dependent storage-forecast test that pinned its clock while the code
under test reads the real one.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
For a one-person homelab, "on call" is when you can be reached. Settings ->
Notifications -> When -> Away holds notifications while you are away (a banner on
every page says so) and sends one digest when it ends, at its time or when you say
you are back. Critical alerts can still come through. Quiet hours get the same
"still send critical alerts" option. Escalation steps marked to send in quiet hours
are sent while away too. What is held for one reason is not released while the
other still holds it.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Monitoring -> Service levels: a target (99.9 %) on an endpoint check, a server or an
integration, measured over calendar months. Shows the figure, downtime used, the
error budget left, and how the last six months went. 80 % of the budget used is a
warning and an overspent budget a critical alert. Endpoints are measured day by day,
servers and integrations to the minute from the audit log.
The report page gains Quarter and Year (same figures, with a Service levels section),
and two settings send the quarterly and annual report after the month that ends them.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Each server's CPU load and memory use get a baseline for every hour of the week
(median and robust spread over up to ten weeks, four needed). A clearly high last
hour that never dropped back toward normal is a warning; everything else stays
quiet. Server History -> Trends draws a usual line and band. Setting under
Notifications, on by default.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>