Speedtest Tracker, Costs, "Having trouble" on status pages, grouped Integrations and Dashboard
- 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>
This commit is contained in:
1 parent
78822346b1
commit
f86661f6c9
49 files changed
+18156
-238
No files matched your search
@@ -402,6 +402,17 @@ osTicket's API cannot close a ticket, so this is the one place in the app that *
|
||||
- `/metrics` has `homelab_hetzner_server_running`, `homelab_hetzner_traffic_outgoing_bytes`, `homelab_hetzner_traffic_included_bytes` and `homelab_hetzner_monthly_cost`.
|
||||
- **Not verified against a live project** — the endpoints (`/servers`, `/volumes`, `/images?type=snapshot` and `type=backup`, `/primary_ips`, `/pricing`) and their fields are as Hetzner's published OpenAPI file has them, and the reader is tried against a pretend server. **Traffic** is read as bytes and shown in binary units (Hetzner's 20 TB is 20 TiB); a server's *included* traffic and the *outgoing* traffic of the current billing month come from the server itself. The **cost** is the list price including VAT (the `gross` prices): check it against Hetzner's invoice the first time. Dedicated (Robot) servers and Hetzner Storage Boxes are a different API and are not read.
|
||||
|
||||
### Speedtest Tracker
|
||||
|
||||
- **Config fields:** the **address** of Speedtest Tracker (`http://speedtest.example.lan`) and an **API token** (the profile menu → *API tokens* → create one with the **results:read** ability; stored encrypted — that is all it needs). Optional: **the download and upload you pay for** (Mbit/s) and **the share below which to warn** (60% unless you say), which the alerts use, and, for an https address with a certificate of its own, *insecure*.
|
||||
- **Required access:** read only. The app asks for `/api/healthcheck` (no login) and `/api/v1/results` and only ever sends GET requests — **no speed test is started** (that would be `POST /api/v1/speedtests/run`, which is never called).
|
||||
- **What it does:** every **ten minutes** the newest results are read (three pages of 30 the first time, so there is a past to chart) and each is stored once for 90 days: when, download and upload, ping. The **Speedtest** page shows the latest test, the middle of the last three and charts of speed and ping over 1, 7, 30 or 90 days.
|
||||
- **Alerts** (source *Speedtest*, category *Monitoring*; held back by maintenance on the integration): **the internet is slow** — the *middle* of the newest three completed tests is under the share (60%) of what you pay for, judged separately for download and upload and only for one whose number you gave; and **the speed tests are failing** — the newest three all failed (the internet is down, or Speedtest Tracker cannot reach Ookla). One slow test is not an alert: the middle of three is what is judged.
|
||||
- If Speedtest Tracker cannot be read for 45 minutes its alerts are neither raised nor cleared, and the Alerts page says it could not check.
|
||||
- On a **status page** the integration reads as the internet: *Working*, *Having trouble* when it is slow, *Not working* when the tests are failing.
|
||||
- `/metrics` has `homelab_speedtest_download_bits_per_second`, `homelab_speedtest_upload_bits_per_second` and `homelab_speedtest_ping_seconds` for the newest completed test of each.
|
||||
- **Not verified against a live Speedtest Tracker** — the endpoints and fields are read from its own source code (`routes/api/v1/routes.php`, the results controller and resource) and the reader is tried against a pretend server. `download` and `upload` are bytes per second there (the bits fields are used when present); a result's time is the one Ookla gives in its data, else `created_at`, taken as UTC. Speedtest Tracker may allow fewer than 30 results a page; the reader asks again without a size when it says so.
|
||||
|
||||
### NetBox
|
||||
|
||||
- **Config fields:** the **address** of NetBox (`https://netbox.example.lan`), an **API token** (your profile → API Tokens; stored encrypted; **write enabled off** is enough — both the older `Token` tokens and NetBox 4.5's `nbt_…` tokens work) and, for an https address with a certificate you made yourself, *insecure*.
|
||||
|
||||
Reference in new issue
Block a user