Choose which Cloudflare resources are monitored
Monitor the zones, Pages projects and Workers in your Cloudflare account; a resource that hosts a web service you already monitor does not count toward the plan.
Once the Cloudflare connection is created, on the same tab you choose which zones, Pages projects and Workers ARGUNIS monitors. It works the same as with the other clouds.
ARGUNIS only reads Cloudflare: it never changes DNS, WAF rules or deployments.
What is monitored
Resource | Goes in | Status | Metrics |
|---|---|---|---|
DNS zone | Other hosts | Active, pending, paused or moved; a certificate expiring in less than 14 days leaves the zone "with alerts" | Requests, 5xx errors, blocked threats and bandwidth |
Pages (project) | Servers | The latest production deployment: if it failed, it opens an incident (like Railway) | — |
Worker | Other hosts | Published | Invocations, errors and p90 CPU |
On a zone's page, the DNS tab shows its records (read-only).
A single monitor per site
If the resource serves a web service you already monitor (for example, the page that lives in a Pages project, or a site in the zone), ARGUNIS links it to that web service and it does not count toward the plan: only one monitor is counted, the web service's. In the selection you see it as "The web service … lives here". On the resource's page, Configure → Web or TCP service that lives here lets you change it or release it (releasing it makes it count again).
Choose the resources
Go to Settings → Monitoring → Cloud services and open the Cloudflare tab.
In Cloudflare resources, leave Accounts empty (the connection's account or the ones the token can see) or enter the Account IDs. Click Query.
Check Monitor, choose the place, the group and the interval, and click Save selection.
Cloudflare analytics is free of charge. It arrives a couple of minutes late, so each read looks at the window ending two minutes earlier.