Before you start
Use this project type for a Pages site, not a server runtime.
Create a Cloudflare Pages project in Logister when the monitored surface is the Pages deployment itself: deploy records, build duration, branch, traffic counters, worker or function logs, and site-level checks. If your Pages site also has a separate Node, Ruby, Python, .NET, Android, or iOS backend, create a separate Logister project for that runtime.
| What you need | Why it matters |
|---|---|
| Cloudflare Pages project in Logister | Keeps Pages telemetry separate from app-server telemetry. |
| Project API token | Authenticates manual HTTP events from CI, scripts, Workers, or Pages Functions. |
| Stable service name | Lets Insights and Events group values for the site, such as marketing-site. |
| Release or deployment ID | Connects traffic and build signals to the Pages deployment you are reviewing. |
Current status
Manual telemetry works now; automatic importing is not live yet.
| Available now | Not automatic yet |
|---|---|
| Create a Cloudflare Pages project type. | Pull Cloudflare Web Analytics from the Cloudflare API. |
| Send metrics, logs, check-ins, and deployment records through the HTTP API. | Import top paths, visitors, deployment status, build duration, branch, and failed deployment logs automatically. |
| Store account ID, Pages project name, optional project ID, and credential reference. | Store raw Cloudflare API tokens in the Logister settings form. |
Current importer status
The Rails-side Cloudflare fetcher is not implemented yet. Store importer settings only when you want the project ready for that future job; use manual telemetry when you need data in Logister today.
Where to go
Pick one task.
Today
Send manual telemetry
Use the HTTP API from CI, a script, a Worker, or a Pages Function.
Prepare
Save importer settings
Store Cloudflare identifiers and a credential reference for the future Rails importer.
Verification
A working Pages project shows manual signals in Events and Insights.
- Send one metric from the manual telemetry guide.
- Open the project Events page and filter to
metric. - Open Insights and use the
24hwindow to confirm the event appears in the recent stream. - If you sent a deployment record, open Deployments and confirm the release, environment, branch, and commit match the Pages deploy.
If it is missing
Debug the manual path before changing importer settings.
Importer settings do not make data arrive yet. If a manual event is missing, check the project API token, endpoint URL, payload shape, event type, and rate-limit response. Use the HTTP API guide for request contracts and troubleshooting when an accepted event does not appear where expected.