Document the Technitium DNS integration
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>
This commit is contained in:
1 parent
312093d3f7
commit
a2ff0f7daa
6 files changed
+64
-4
No files matched your search
@@ -19,6 +19,7 @@ This page explains what Homelab Manager watches, how often, how a problem become
|
||||
- [Media managers](#media-managers-sonarr-radarr-prowlarr)
|
||||
- [App versions](#app-versions)
|
||||
- [AdGuard Home](#adguard-home)
|
||||
- [Technitium DNS](#technitium-dns)
|
||||
- [Grafana](#grafana)
|
||||
- [Speedtest](#speedtest)
|
||||
- [NetBox](#netbox)
|
||||
@@ -148,6 +149,7 @@ Every threshold here is a default; where it can be changed, the place is named.
|
||||
| **Hetzner server off / traffic / rescue / backup** | A Hetzner Cloud server that was running is off, is stuck migrating or rebuilding, has used 80% of its month's traffic (critical at 100%), has rescue mode left on, or has backups enabled but none recent | on, with the integration | Hetzner page; [below](#hetzner-cloud) |
|
||||
| **Sonarr / Radarr / Prowlarr** | An application reports a health warning or error, has downloads stuck for two hours, or a disk under 10% free | on, with the integration | Media managers page; [below](#media-managers-sonarr-radarr-prowlarr) |
|
||||
| **AdGuard Home** | DNS has not answered for ten minutes, or its DNS server is not running (critical); protection left off for an hour, or filter lists not updated for a week | on, with the integration | AdGuard Home page; [below](#adguard-home) |
|
||||
| **Technitium DNS** | DNS has not answered for ten minutes, or a secondary zone has expired (critical); a zone cannot sync, blocking left off for an hour, or block lists overdue for an update (warning) | on, with the integration | Technitium DNS page; [below](#technitium-dns) |
|
||||
| **Grafana** | An alert rule is firing (critical when labelled critical or page), a rule cannot be evaluated, or a data source fails its health check | on, with the integration | Grafana page; [below](#grafana) |
|
||||
| **Game server backup / disk / memory** | A Fragnet game server's newest backup is older than the limit (7 days) or none, its disk is over 90% of the plan (critical from 98%), or its memory is over 90% while it runs | on, with the integration | Game servers page; [below](#game-servers-fragnet) |
|
||||
| **Internet slow / speed tests failing** | The middle of the last three speed tests is under the share you set of what the line is sold at (only with those numbers given), or the last three tests all failed | on, with the integration | Speedtest page; [below](#speedtest) |
|
||||
@@ -325,6 +327,20 @@ An integration of type *AdGuard Home* ([INTEGRATIONS.md](../INTEGRATIONS.md#adgu
|
||||
|
||||
"Since when" is **when the app first saw it** in a read. Maintenance on the integration holds the alerts; a reading older than ten minutes is not believed (they are neither raised nor cleared, and the Alerts page says it could not check). `/metrics` has whether it runs, protects and answers, how long an answer took, and the queries and blocked counts.
|
||||
|
||||
## Technitium DNS
|
||||
|
||||
An integration of type *Technitium DNS* ([INTEGRATIONS.md](../INTEGRATIONS.md#technitium-dns)) is read every two minutes, and **Network → Technitium DNS** shows whether DNS answers (a real question over UDP, with how long it took), whether blocking is on, how long the server has run, the last day's queries and how they ended, the clients and names asked about and blocked most, the cache against its limit, the block lists and when they are next updated, the zones that have a problem and the DHCP leases. Nothing is changed. It does not report the CPU, memory or disk of the machine it runs on — Technitium's API has none; a server agent does.
|
||||
|
||||
| Alert | When | Severity |
|
||||
|---|---|---|
|
||||
| **DNS not answering** | The test question has gone unanswered (or been answered with a server failure or a refusal) in every read for **ten minutes**. "No such name" counts as an answer | critical |
|
||||
| **Zone expired** | A secondary zone has expired — it no longer answers. One alert for all the zones with a problem; it is critical if any of them has expired | critical |
|
||||
| **Zone cannot sync** | Secondary zones that cannot sync with their primary and are going stale (none has expired yet) | warning |
|
||||
| **Blocking off** | Blocking has been switched off for **an hour** while block lists are set up — someone paused it and forgot; nothing is being blocked. With no block lists, off is how it is and nothing is said | warning |
|
||||
| **Block lists overdue** | The block lists' next update was due more than **six hours** ago and has not happened | warning |
|
||||
|
||||
The server's own internal zones and zones that are switched off are not judged. "Since when" is **when the app first saw it** in a read. Maintenance on the integration holds the alerts; a reading older than ten minutes is not believed (they are neither raised nor cleared, and the Alerts page says it could not check). `/metrics` has whether it answers and how long an answer took, whether blocking is on, how long it has run, the last day's counts, the cache, the zones with a problem and the DHCP leases.
|
||||
|
||||
## Grafana
|
||||
|
||||
An integration of type *Grafana* ([INTEGRATIONS.md](../INTEGRATIONS.md#grafana)) is read every five minutes, and **Monitoring → Grafana** shows which alert rules are firing, pending or cannot be evaluated, and how each data source tests. Nothing is silenced or changed.
|
||||
|
||||
Reference in new issue
Block a user