Cloudflare monitoring with Topologix

Cloud & CDN

Zone analytics straight from Cloudflare’s GraphQL Analytics API — either an HTTP Requests card (requests, 4xx/5xx, cache hit ratio, and firewall events for a whole zone or a single hostname/path) or a Site Overview card that fans out to five datasets at once: web performance with edge-TTFB percentiles, cache efficiency in requests and bytes, security events by action, DNS analytics, and RUM Core Web Vitals.

Requirements

• A Cloudflare API token with Zone → Analytics → Read on the zones you monitor, plus Account → Analytics → Read for the account-scoped Web Vitals dataset. Use a custom token — not the Global API Key, which is deprecated and overly permissive.
• Dataset availability varies with the zone’s plan: Cloudflare gates some GraphQL datasets and their retention windows by tier (Free covers the HTTP basics; some datasets need a Pro or Business zone). A gated dataset degrades its overview section to “not available” instead of failing the source.
• Two overview sections carry prerequisites of their own: DNS analytics needs the zone’s DNS hosted on Cloudflare, and Core Web Vitals needs a Web Analytics site tag.

1 · Set up the integration

1. Open the Integrations pageClick Integrations in the toolbar and pick Cloudflare from the catalogue.
2. Create a custom tokenCloudflare dashboard → My Profile → API Tokens → Create Token → Create Custom Token. Permissions: Zone → Analytics → Read and Account → Analytics → Read; Zone Resources: include the zones you want to monitor. Tokens can be rotated at any time from the same screen.
3. Paste and testThe drawer has exactly one field — API Token. Click Create, then reopen the integration and click Test — it lists the zones the token can see and reports “Connected. Found N zone(s).”

2 · Add it to a flow

1. Select the nodeClick the node, open Metrics, then + Add and choose the Cloudflare integration.
2. Pick the type and zoneA Type toggle chooses HTTP Requests or Site Overview, and the DNS Zone dropdown is filled from the token (or paste a zone ID). Requests mode adds an optional URL / Host filter — a hostname, or a path starting with /, with * wildcards; overview mode adds the optional Web Analytics site tag that switches on the Core Web Vitals section.
3. SavePick the period (1 minute to 24 hours — overview enforces at least 5 minutes, because it fans out ~5 queries against datasets that lag a little) and click Add Source.

Good to know

• Every Site Overview dataset is its own GraphQL query behind Promise.allSettled — a dataset the token, zone, or plan can’t serve nulls only its section, never the whole tick.
• Cache hit ratio counts hit, stale, updating, and revalidated as cached — the same statuses Cloudflare itself treats as “served from cache”.
• A filter starting with / matches the request path, anything else matches the request host, and * becomes a GraphQL wildcard — so /api/v1/* and *.example.com both work.