CF Monitor

What CF Monitor includes

• One-line SDK wrapper

  import { monitor } from '@littlebearapps/cf-monitor' — wraps fetch, cron, and queue handlers. Auto-detects worker name, feature IDs, and all 8 binding types. Zero config needed.

• Three-tier circuit breakers

  Per-invocation limits (immediate), daily budgets (hourly enforcement), and monthly budgets (billing-period-aware). Feature-level, account-level, and global kill switches.

• Zero D1, zero queues

  Analytics Engine for metrics (100M writes/month free), KV for state. No database migrations, ever. The monitor worker itself costs ~265 KV ops/day.

• Error collection + GitHub issues

  Tail worker captures errors from all monitored workers. FNV fingerprinting deduplicates. Auto-creates GitHub issues with P0-P4 priority labels. Bidirectional webhook sync.

• 8 binding types tracked

  D1 (reads, writes, rows), KV (reads, writes, deletes, lists), R2 (Class A, Class B), Workers AI (requests, neurons), Vectorize, Queue, Durable Objects, and Workflows — all automatic.

• Plan-aware budgets

  Auto-detects Workers Free vs Paid plan via Subscriptions API. Selects correct budget defaults per plan. Monthly budgets align to your actual billing period, not calendar months.

• Account usage dashboard

  Hourly GraphQL queries for 5 services (Workers, D1, KV, R2, Durable Objects). Shows percentage of plan allowance used. GET /usage endpoint and npx cf-monitor usage CLI.

• Slack alerts with dedup

  Budget warnings (70%, 90%, 100%), gap alerts, cost spike detection, and self-monitoring staleness alerts. All deduplicated via KV to prevent alert fatigue.

• Self-monitoring

  cf-monitor monitors itself — tracks cron execution, error counts, and handler staleness. GET /self-health returns 200 when healthy, 503 when stale. Slack alerts if crons stop running.

• Worker auto-discovery

  Daily cron discovers all workers on the account via Cloudflare API. No manual registry — new workers appear automatically. npx cf-monitor coverage shows monitored vs unmonitored.

• 10-command CLI

  init, deploy, wire, status, coverage, secret, usage, config sync, config validate, upgrade. From zero to fully monitored account in 3 commands.

• Security hardened

  Admin endpoint auth (timing-safe token comparison), CLI command injection prevention, webhook replay protection, GraphQL input validation, markdown escaping, and module-private symbols.

cf-monitor vs centralised monitoring

• • 1 worker per account instead of 10+ platform workers and agents.
• • Analytics Engine + KV only — no D1 database, no 61 migrations, ever.
• • 1 cf-monitor.yaml instead of services.yaml + budgets.yaml + sync script.
• • 3 CLI commands to set up instead of 7+ manual steps.
• • 1 export (monitor()) instead of 18 sub-path exports.
• • Each account is self-contained — no cross-account HMAC forwarding needed.

Roadmap