IT OPS

Cloudflare Pages bloat threshold monitor with Axiom log and PagerDuty alert

Hourly, measures total Cloudflare Pages deployment storage per project against a budget threshold, records the reading in Axiom.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerHourly schedule starts the check
  • ActionFetch deployment inventory and sizesCloudflareCloudflare
  • LogicSum storage and compare to per-project budget
  • ActionLog per-project storage reading to AxiomAxiom
  • OutputPage on-call via PagerDuty when over budgetPagerDutyPagerDuty

What it does

This template monitors rather than deletes. Each hour it sums the storage held by all deployments in each Cloudflare Pages project, compares the total against a per-project budget, and logs the measurement to Axiom for time-series tracking. When a project exceeds its threshold it opens a PagerDuty incident so on-call can decide whether to run a sweep, raise the budget, or investigate a runaway preview branch.

When to use it

Use this to catch storage bloat early instead of discovering it on a billing statement, and to keep a continuous record of per-project growth across your Pages account.

How it works

  1. 1An hourly schedule starts the check.
  2. 2Cloudflare returns deployment inventory and sizes per project.
  3. 3A logic step sums storage and compares each project to its budget.
  4. 4Axiom ingests the per-project storage reading every run.
  5. 5If any project is over budget, PagerDuty opens an incident with the project, current usage, and overage.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect AxiomLog streams, queries, dashboards.
  3. 3
    Connect PagerDutyIncidents, on-call, escalations.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.