DumbMonit
IntegrationsSecurity and identity
Monitor Pi-hole with DumbMonit
The DNS ad blocker: blocking on or paused, queries and share blocked, blocklist age, upstream failures, updates and its own diagnosis messages.
DocumentationOfficial website: Pi-hole
Product descriptions are in English, as in the product. The page labels follow your language.
What DumbMonit watches
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.
Typical use. DNS ad blocker: blocking state, blocked share, blocklist age, updates
Examples
- Pi-hole v6 on a Raspberry Pi
- Pi-hole in Docker
How it connects
What you need
- App password (recommended)Generated under Settings → Web interface / API in expert mode. It cannot change Pi-hole's settings.
No account needed.
Network ports to open
80/TCPAPI (HTTP, default)443/TCPOnly with the https scheme option
Setup steps: 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.
Heads-up. 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.