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
@@ -317,6 +317,14 @@ All gauges. The same table is checked by a test against what `/metrics` really s
|
||||
| `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. |
|
||||
| `homelab_technitium_dns_up`, `homelab_technitium_blocking_enabled` | `name` | 1 if Technitium's DNS server answered the app's test DNS question, and if its blocking is on; else 0. |
|
||||
| `homelab_technitium_dns_probe_seconds` | `name` | How long it took to answer that question; left out when it did not. |
|
||||
| `homelab_technitium_uptime_seconds` | `name` | How long the DNS server has run, since it last started; left out when it did not say. |
|
||||
| `homelab_technitium_block_lists_overdue` | `name` | 1 if the block lists' update was due more than six hours ago, else 0. Only where block lists are set up. |
|
||||
| `homelab_technitium_queries`, `homelab_technitium_blocked`, `homelab_technitium_cached`, `homelab_technitium_recursive`, `homelab_technitium_server_failures`, `homelab_technitium_clients` | `name` | The last day's queries, how many were blocked, answered from the cache, resolved by the server and ended in a server failure, and how many different clients asked. Gauges over a rolling day, not counters. |
|
||||
| `homelab_technitium_cache_entries` | `name` | Entries in its DNS cache now. |
|
||||
| `homelab_technitium_zones`, `homelab_technitium_zone_problems` | `name` | The zones it holds (its internal ones not counted), and how many have expired or cannot sync. |
|
||||
| `homelab_technitium_dhcp_leases` | `name` | The DHCP leases it holds. Left out when it has no DHCP server. |
|
||||
| `homelab_grafana_rules`, `homelab_grafana_rules_firing`, `homelab_grafana_rules_error` | `name` | How many alert rules Grafana has, how many are firing and how many cannot be evaluated. |
|
||||
| `homelab_grafana_datasources_failing` | `name` | How many of Grafana's data sources fail its health check. |
|
||||
| `homelab_fragnet_server_running` | `account`, `server`, `game` | 1 if the Fragnet game server is running, else 0. |
|
||||
|
||||
Reference in new issue
Block a user