Lidarr/Readarr, integration inspector, app versions, grouped alerts
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>
This commit is contained in:
1 parent
551eb1597a
commit
93aaf5476d
45 files changed
+10033
-65
No files matched your search
+15
-1
@@ -17,6 +17,7 @@ This page explains what Homelab Manager watches, how often, how a problem become
|
||||
- [Hetzner Cloud](#hetzner-cloud)
|
||||
- [Game servers (Fragnet)](#game-servers-fragnet)
|
||||
- [Media managers](#media-managers-sonarr-radarr-prowlarr)
|
||||
- [App versions](#app-versions)
|
||||
- [AdGuard Home](#adguard-home)
|
||||
- [Grafana](#grafana)
|
||||
- [Speedtest](#speedtest)
|
||||
@@ -162,6 +163,7 @@ Every threshold here is a default; where it can be changed, the place is named.
|
||||
| **Docker image has critical vulnerabilities** | Dockhand's own scans of a Docker host's images found one or more *critical* findings (high, medium and low are only shown — unless you set a number for high ones, below) | on | Settings → Notifications; [below](#docker-containers-that-are-broken) |
|
||||
| **Docker host has many high vulnerabilities** | The same scans found at least the number of *high* findings you set (*Also warn when a Docker host has this many high vulnerabilities*; 0, the default, never) | off | Settings → Notifications; [below](#docker-containers-that-are-broken) |
|
||||
| **Docker host has old running images** | A Docker host has running containers whose images were built more than the number of days you set ago (*Warn about running Docker images that were built more than …*; 0, the default, never) — scanned or not | off | Settings → Notifications; [below](#docker-containers-that-are-broken) |
|
||||
| **App behind its newest release** | An application has had a newer release out for the number of days set under Operations → App versions (0, the default, never) — needs the lookup of releases switched on | off | App versions page; [below](#app-versions) |
|
||||
| **Automation failed** | A Semaphore template's or Gitea repository's latest run failed (a run still going or cancelled does not count) | | not configurable |
|
||||
| **Integration failing** | An integration's calls have failed several times in a row ([Integrations](#integrations)) | 3 calls | Settings → Notifications |
|
||||
| **Endpoint check failing / certificate running out** | See [below](#endpoint-checks-and-heartbeats) | | per check |
|
||||
@@ -288,7 +290,7 @@ Hetzner does not say when a server went off or when rescue mode was switched on,
|
||||
|
||||
## Media managers (Sonarr, Radarr, Prowlarr)
|
||||
|
||||
An integration of type *Sonarr*, *Radarr* or *Prowlarr* ([INTEGRATIONS.md](../INTEGRATIONS.md#sonarr-radarr-and-prowlarr)) is read every five minutes, and **Apps → Media managers** shows, for each: what the application says is wrong with itself, its download queue (the stuck ones first, with why), its disks, how many wanted items have no file (Sonarr, Radarr) and, for Prowlarr, which indexers it has switched off after failures. Nothing is searched, grabbed or changed.
|
||||
An integration of type *Sonarr*, *Radarr*, *Prowlarr*, *Lidarr* or *Readarr* ([INTEGRATIONS.md](../INTEGRATIONS.md#sonarr-radarr-and-prowlarr)) is read every five minutes, and **Apps → Media managers** shows, for each: what the application says is wrong with itself, its download queue (the stuck ones first, with why), its disks, how many wanted items have no file (Sonarr, Radarr) and, for Prowlarr, which indexers it has switched off after failures. Nothing is searched, grabbed or changed.
|
||||
|
||||
| Alert | When | Severity |
|
||||
|---|---|---|
|
||||
@@ -335,6 +337,18 @@ An integration of type *Grafana* ([INTEGRATIONS.md](../INTEGRATIONS.md#grafana))
|
||||
|
||||
Grafana can notify about its own alerts as well; with both switched on you hear twice. Maintenance on the integration holds the alerts; a reading older than 20 minutes is not believed. `/metrics` has the rules, those firing, those in error and the failing data sources.
|
||||
|
||||
## App versions
|
||||
|
||||
**Operations → App versions** lists each connected application whose version is known, with the newest release of it and how far behind it is: *a patch* (the third number), *a minor update* (the second), *a major version* (the first; for Authentik, whose versions are dates, a new year). A build number after the third number is ignored, and prefixes (`v`, `n8n@`, `version/`) are taken off. What is newer here than the newest release (a beta) is *ahead*.
|
||||
|
||||
The newest release is asked of **GitHub** (`GET /repos/{owner}/{repo}/releases/latest`, which leaves out pre-releases and drafts) **once a day, and only for an application whose version has been read** — and **only while an administrator has switched the lookup on**. It sends nothing about you or your systems but the name of the repository, and is the only thing this app asks of an address that is not yours. GitHub limits requests without a sign-in (60 an hour); a lookup that is refused keeps the release it had, says why on the page and is tried again at the next pass.
|
||||
|
||||
| Alert | When | Severity |
|
||||
|---|---|---|
|
||||
| **App behind its newest release** | A newer release has been out for the number of days set (*Warn when a newer release has been out for … days*; 0, the default, never) and the application has not caught up. The alert says which release, how long, and whether it is a patch, a minor update or a new major version | warning |
|
||||
|
||||
Maintenance on the integration holds the alert. It is under *Updates* on the Alerts page. `/metrics` has `homelab_app_update_available` (1 if a newer release is out) for each application, while the lookup is on.
|
||||
|
||||
## Speedtest
|
||||
|
||||
An integration of type *Speedtest Tracker* ([INTEGRATIONS.md](../INTEGRATIONS.md#speedtest-tracker)) is read every ten minutes, and **Monitoring → Speedtest** shows the newest test, the middle of the last three and charts of download, upload and ping over up to 90 days. This app never starts a test: Speedtest Tracker runs them on its own schedule.
|
||||
|
||||
@@ -313,6 +313,7 @@ All gauges. The same table is checked by a test against what `/metrics` really s
|
||||
| `homelab_arr_queue_items`, `homelab_arr_queue_stuck_items` | `app`, `name` | The downloads in the queue of Sonarr or Radarr, and how many are stuck (judged wrong, failed or blocked for two hours or more). |
|
||||
| `homelab_arr_wanted_missing` | `app`, `name` | Wanted items Sonarr or Radarr has no file for. |
|
||||
| `homelab_arr_disk_free_bytes` | `app`, `name`, `path` | Free space of a disk Sonarr, Radarr or Prowlarr uses. |
|
||||
| `homelab_app_update_available` | `app`, `name`, `running`, `latest` | 1 if a newer release of the application is out than the one it runs, else 0. Only while Operations → App versions is switched on, and for an application whose newest release has been looked up. |
|
||||
| `homelab_adguard_running`, `homelab_adguard_protection_enabled`, `homelab_adguard_dns_up` | `name` | 1 if AdGuard Home's DNS server runs, if its protection is on, and if it answered the app's test DNS question; else 0. |
|
||||
| `homelab_adguard_dns_probe_seconds` | `name` | How long it took to answer that question; left out when it did not. |
|
||||
| `homelab_adguard_queries`, `homelab_adguard_blocked`, `homelab_adguard_avg_processing_seconds` | `name` | The queries it answered in its statistics period, how many it blocked, and its average processing time. |
|
||||
|
||||
Reference in new issue
Block a user