DumbMonit

IntegrationsCloud and domains

Monitor Cloudflare with DumbMonit

Zones, tunnels, certificates, traffic errors and load balancer pools of a Cloudflare account, read through the Cloudflare API.

DocumentationOfficial website: Cloudflare

Product descriptions are in English, as in the product. The page labels follow your language.

What DumbMonit watches

The zones of a Cloudflare account through the Cloudflare API: zones that are no longer active, tunnels that went down or degraded, certificates about to expire, a rise of 5xx responses and unhealthy load balancer pools. DumbMonit reads the API at api.cloudflare.com/client/v4 once a minute with a read-only API token sent as a bearer token. Only the list of zones is required; every other part (tunnels, certificates, traffic, load balancers) needs its own read permission and is skipped, without making the monitor fail, when the token lacks it or the plan does not include the feature. The calls made for each zone are limited to the first 50 active zones and sent five at a time, far below…

Typical use. Zones, tunnels, certificates, 5xx errors, load balancer pools

Examples

  • Cloudflare zones and tunnels

How it connects

What you need

  • API tokenA Cloudflare API token with read-only permissions.

Network ports to open

  • 443/TCPCloudflare API (HTTPS, api.cloudflare.com)
Setup steps: Create a read-only API token for DumbMonit
  1. In the Cloudflare dashboard, open My Profile > API Tokens > Create Token > Create Custom Token, and name it DumbMonit.

  2. Add the read-only permissions listed below, and nothing else. The first one is required; the others switch on one part each.

  3. Under Account Resources and Zone Resources, choose the account and the zones to monitor (All zones is fine).

  4. Click Continue to summary > Create Token, then copy the token: it is shown once.

  5. In DumbMonit, use this address and paste the token as API token. Leave Account ID empty unless the token covers several accounts.

    api.cloudflare.com

Heads-up. A part whose permission is missing (or that the plan does not include) is skipped and its readable metric is 0; it does not make the monitor fail. Only the zones the token can see are watched.