DumbMonit
IntegracionesSeguridad e identidad
Monitorizar Pi-hole con DumbMonit
The DNS ad blocker: blocking on or paused, queries and share blocked, blocklist age, upstream failures, updates and its own diagnosis messages.
DocumentaciónSitio web oficial: Pi-hole
Las descripciones están en inglés, como en el producto. Las etiquetas de la página siguen su idioma.
Qué vigila DumbMonit
The DNS ad blocker: whether it is blocking, how many queries it answers and blocks, how old its blocklists are, whether its upstream resolvers fail, whether an update waits, and the messages of its own diagnosis page.
Uso habitual. DNS ad blocker: blocking state, blocked share, blocklist age, updates
Ejemplos
- Pi-hole v6 on a Raspberry Pi
- Pi-hole in Docker
Cómo se conecta
Qué necesita
- App password (recommended)Generated under Settings → Web interface / API in expert mode. It cannot change Pi-hole's settings.
No hace falta ninguna cuenta.
Puertos de red que abrir
80/TCPAPI (HTTP, default)443/TCPOnly with the https scheme option
Pasos de configuración: Create an app password in Pi-hole
In Pi-hole's web interface, open Settings → Web interface / API and switch the page from Basic to Expert.
Click Configure app password, copy the password shown, then click Enable new app password.
Check that Settings → All settings → Webserver and API → webserver.api.app_sudo is off, its default.
In DumbMonit, enter Pi-hole's address and paste the app password, or pick No password if the web interface has none.
Ojo. Pi-hole v6 or later is required; the app password can still pause blocking and edit lists through the API, so keep it for DumbMonit only.