How to use a Righthand with Cloudflare

Quick answer

Use Righthand to prepare a Cloudflare analytics review for one zone or application. Separate edge traffic observations from evidence that the origin application served the customer's task.

Start with a reviewable deliverable, keeping Cloudflare as the accepted home for its records. This guide uses an explicitly approved snapshot or browser read; it does not assume that every provider API action is exposed by your Righthand connection.

Evidence and access

Cloudflare documents analytics for its services. See the official Cloudflare reference. Provider capabilities and Righthand's available tools are separate checks.

Use the owner's limited zone or Worker inventory, deployment references, routes, and supplied request receipts; exclude unrelated accounts and zones. Verify the required tools and owner-approved scope through Righthand integrations; use the supplied packet when a native read is unavailable.

Define the objects and authority

Include these fields in the working input: zone or account ID, dataset, time window, dimensions, request counts, error category, source timezone. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

Edge metrics have their own definitions. Do not infer origin health, customer success, or authority to change firewall rules from traffic totals.

Illustrative first-run brief

Use the owner-provided Cloudflare snapshot or approved read-only view. Review the supplied zone report for the approved incident window. Group observed errors and missing dimensions. Draft investigation questions without altering DNS, cache, or security rules. Run once for the agreed sample, using America/Los_Angeles for the review deadline and preserving source timestamps separately. Return the draft in this conversation by Friday at 3 PM Pacific for the infrastructure owner to review. Include source references and missing fields. Do not write records, spend money, change permissions, or send external messages. Stop and report an unavailable source rather than substituting another account.

Expected result and verification

A rise in edge errors prompts investigation but does not establish the application cause. An absent dataset is reported as missing coverage.

Compare one aggregate with the original dataset and same filter set. Record the source cutoff, applied filters, and items excluded from the sample. The reviewer should be able to follow each consequential finding back to an original object. A well-written summary is not evidence that a proposed action happened. If a later write is authorized, verify its specific result separately before changing the task's status.

Illustrative input and draft output

These synthetic entries show the requested review, not live account results or a provider field schema.

Common failure and recovery

Different services use different analytics scopes. Align zone, account, and dataset before joining reports or labeling an outage.

When route or DNS evidence conflicts, name the zone and observed target and ask the administrator to reconcile it before any proposed change.

FAQ

What should the reviewer verify first?

Verify account, zone, route, deployment version, and the actual request evidence. A configuration entry is not proof that customer traffic reached the intended code.

How should a repeat run be scoped?

Preserve zone IDs, routes, version references, and observation times. Repeat the customer-path check after approved routing changes; do not infer adoption from configuration alone.

For connection and permission details, use Righthand Docs. Review Pricing alongside any separate provider charges before expanding the workflow.