Projects

Monitoring & alarms

Usage metrics, deploy history, runtime errors, the audit log, and threshold alarms that notify you before a project hits a limit.

Usage

Each org and project surfaces resource usage — requests, D1 reads/writes, R2 storage — sourced from Cloudflare Analytics. The dashboard’s metric cards and the project Usage tab read from the same data. When live analytics aren’t available yet (a brand-new project), the cards show — until the first metrics land.

Alarms

An alarm fires a notification (and any subscribed webhooks / integrations) when a usage metric crosses a threshold — so you hear about it before a hard limit does.

curl -X POST https://cloud.backlex.com/api/org/<org>/projects/<project>/alarms \
  -H "Authorization: Bearer pak_..." \
  -H "Content-Type: application/json" \
  -d '{"metric":"requests","thresholdPct":80}'

Field	Values
`metric`	`requests`, `d1`, `r2`
`thresholdPct`	`1`–`100` — percent of the plan limit

Alarms are evaluated on a schedule; when one trips, an alarm.fired event is emitted. Creating/deleting alarms needs the developer role or above.

Deploys

Every provision, branch, and re-deploy writes a deploy record (version, status, trigger, actor). The project Deploys view is the timeline — handy for correlating a behavior change with a release.

Runtime errors

The project Errors view aggregates runtime errors reported from the instance, so you can spot a misbehaving deploy without leaving the console.

Audit log

Every state-changing action across the org — project lifecycle, member changes, key creation, SSO config, billing — is recorded with the actor, target, payload summary, and source IP. Filter by action and time range in the Audit log, or via:

curl "https://cloud.backlex.com/api/org/<org>/audit?action=project.create&limit=50" \
  -H "Authorization: Bearer pak_..."