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
@@ -13,6 +13,16 @@ the dashboard views themselves load fine. (UniFi, Nginx Proxy Manager, Home Assi
|
||||
|
||||
## Integrations
|
||||
|
||||
### Checking what an integration can read
|
||||
|
||||
On the Integrations page an administrator has an **Inspect** button on each integration that reads through the shared HTTP helper (Authentik, Immich, Jellyfin, NetBox, Nextcloud, Paperless-ngx, Prometheus, Hetzner Cloud, Speedtest Tracker, Fragnet, Sonarr, Radarr, Prowlarr, Lidarr, Readarr, AdGuard Home and Grafana). It runs the integration's reader once and shows:
|
||||
|
||||
- **what was asked** — each request, its path (with the *names* of the query parameters, not their values), the status, how long it took and how many bytes;
|
||||
- **what came back** — the *shape* of each JSON answer to three levels: the names of the fields and the kind of each (`string`, `number`, `array(12) of { … }`), with a `?` on a field that only some items of a list have. Never a value, never a token, so the report can be copied into a message;
|
||||
- **what the reader made of it**, in the same way, and **where that is empty** — a field that is null, an empty text, an empty list, or null in every item of a list. A reader that expects a field the system names differently ends up here.
|
||||
|
||||
It is for the readers written from documentation (see "Not verified" on each integration): put what came back beside what is empty and a mismatch is plain. Something being empty is often right — no containers, nothing wrong — so it is a list to look at, not a verdict. Each inspection is in the audit log; nothing is stored. Only an administrator can run it, and it times out after 90 seconds.
|
||||
|
||||
### Tailscale
|
||||
|
||||
- **Config fields:** Tailnet, API key
|
||||
@@ -396,6 +406,7 @@ osTicket's API cannot close a ticket, so this is the one place in the app that *
|
||||
### Sonarr, Radarr and Prowlarr
|
||||
|
||||
- **Config fields:** the application's **URL** and its **API key** (in the application: Settings → General → Security → API Key; stored encrypted), and *Allow self-signed certificate* if it is on HTTPS with its own certificate. Add each application as its own integration, as the kind it is — the *Test* button says if the address turns out to be another one. The key is sent as `X-Api-Key`; the app only ever sends GET requests.
|
||||
- **Lidarr and Readarr** (music and books) are the same: add them as their own kinds. They answer under `/api/v1` (as Prowlarr does), and ask for their own unknown items in the queue (`includeUnknownArtistItems`, `includeUnknownAuthorItems`). The *Test* button says if an address is another one of the family. Readarr's own project has been retired; the integration reads whatever install you still run.
|
||||
- **Required access:** the application's address reachable from the app. Sonarr and Radarr answer under `/api/v3`, Prowlarr under `/api/v1`. A read is five to six requests, every five minutes.
|
||||
- **What it does:** every **five minutes** each application is read — its version, what its own checks found (`/health`), its **download queue** (`/queue`: the first 100, and how many there are), its **disks** (`/diskspace`), for Sonarr and Radarr how many **wanted** items have no file (`/wanted/missing`), and for Prowlarr its **indexers** and which it has switched off after failures (`/indexer`, `/indexerstatus`). **Apps → Media managers** shows them. Nothing is searched, grabbed, removed or changed.
|
||||
- **Alerts** (sources *Sonarr*, *Radarr*, *Prowlarr*; held back by maintenance on the integration): what the application **says is wrong** with itself (a finding of type warning or error — a download client that cannot be reached, a root folder gone, indexers unavailable; a *notice*, such as an update being available, is shown but not raised); **downloads that are stuck** (in the queue for two hours or more and judged warning or error, failed, or blocked from importing — one alert for the lot, naming the first three and why); a **disk nearly full** (under 10% free, critical under 5%; folders on one disk count once, and a disk under 2 GB is not a media disk). See [MONITORING.md](docs/MONITORING.md#media-managers-sonarr-radarr-prowlarr).
|
||||
|
||||
Reference in new issue
Block a user