Analytics

Once something is published, the Analytics app answers the next question: is anyone reading it? It shows the traffic Cloudflare's edge saw for the hostnames this node publishes: the same list as My Apps, VM ports, local services, the homepage and redirects alike.

• For you: which name is busy, which pages are asked for, from which countries and with which browsers, and whether a crawler is hammering a site or a server is answering with errors.
• Nothing to add to a site. The numbers are Cloudflare's own count, read with the node's token. Nothing goes into your pages.
• For an agent: the same numbers are one HTTP call, so an agent that published a site can check that it is being reached and is not answering with errors.

Publishing to the web is how a name gets here; this chapter is about who came.

Open it

Double-click the Analytics icon on the desktop, or choose Analytics… from the Cloudflare module's menu in the Control Strip.

The app reads Cloudflare's analytics with the node's own token, which needs Zone → Analytics → Read on top of the wizard's two permissions. Without it the window says so. The numbers are those of the zone chosen in the Cloudflare setup: a name published in another zone is listed, but its traffic is not counted here.

The window has, from the top: the span buttons and the host pop-up, six tiles, a chart, and ranked lists. The status line names your domain and the span, and says when the numbers were last updated.

Choose a span and a host

• Span: click 1 Hour, 24 Hours, 7 Days or 30 Days.
• Host: pick one in the pop-up, or All Hosts. Clicking a host's row in Hosts picks it too; click it again for all of them.

The pop-up lists each host beside its icon, the one My Apps shows: the app's touch icon or favicon, the homepage's for the names that redirect to it, and a diamond for an app that declares none.

What the tiles count

Each tile also shows its change against the span before it. 30 Days has no span before: Cloudflare keeps these numbers 31 days.

Stopped requests

Stopped is what Cloudflare's security answered itself: a challenge page or a block, from a rule of your own in the zone's WAF, a managed rule or the browser check.

Those requests never reached your host, but they are in Requests too, since Cloudflare counts every request that reached its edge. A crawler that keeps hammering a challenge shows as a Requests line with a Stopped line close under it. Hosts can rank by Stopped, to see which name draws them.

Read the chart

The chart draws requests, visits and stopped requests over the span. Point at it to read one point. The last points, which Cloudflare is still counting, are drawn pale.

The chart follows the view picked in Hosts. Requests and Visits draw requests, visits and stopped requests together. Data, Errors and Stopped draw data served, server errors or stopped requests alone, on a scale of their own, and the reading under the pointer says the same.

The ranked lists

Under the chart are ranked lists for the chosen hosts. The buttons beside a list's name pick its view.

A Host header that carries a port (scanners try Cloudflare's other ports) counts with its host.

Narrow to one kind of bot

Click a row in Bots to narrow everything to that category, keeping the chosen host. The tiles, the chart, the host totals and the other lists then count only, say, AI crawlers, and the status line says so.

The Bots list itself stays whole, so another category is one click away. Click the chosen row again to lift the filter.

How fresh the numbers are

• The window refreshes every minute while it is open, and the daemon keeps each answer a minute, so several windows cost one query.
• Switching is quick because answers are kept twice over. The window paints a view it has shown before from memory and then brings it up to date.
• The daemon, behind an All Hosts answer, fetches the view of each host that had traffic (the twelve busiest at most), so the first switch to a host needs no trip to Cloudflare.
• An answer up to 15 minutes old is shown at once while a fresh one is fetched; the status line says "Updating…".
• Busy spans are sampled by Cloudflare, and the status line says "sampled".

The same numbers for an agent

GET /v1/cloudflare/analytics?range=24h&host=…&bot=… returns what the window shows: the totals, those of the span before, the chart's points, every host's totals and the ranked lists.

• range is 1h, 24h, 7d or 30d.
• host is one published name; leave it out for all of them.
• bot is one of Cloudflare's verified bot categories, such as AI Crawler; leave it out for all traffic.

The Agent Skill Guide (Help → Agent Skill Guide…) describes the answer field by field.