Integrate Cloudflare edge analytics ingestion #18

New issue

Open

opened 2026-07-01 01:01:19 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-01 01:01:19 +00:00

(Migrated from github.com)

Problem

We deliberately avoid logging every request to MySQL for privacy and cost reasons. Usage stats must come from Cloudflare edge analytics via its API/GraphQL.

Acceptance criteria

A scheduled job pulls request counts from the Cloudflare analytics API for the relevant zone
Pulled metrics are stored as aggregates (per key/route/time-bucket), not per-request rows
API credentials are stored as secrets, never committed, and never exposed to the SPA
The job is idempotent and tolerates gaps/retries without double-counting

Notes

Privacy-first: aggregate only, no per-request PII retention.

## Problem We deliberately avoid logging every request to MySQL for privacy and cost reasons. Usage stats must come from Cloudflare edge analytics via its API/GraphQL. ## Acceptance criteria - [ ] A scheduled job pulls request counts from the Cloudflare analytics API for the relevant zone - [ ] Pulled metrics are stored as aggregates (per key/route/time-bucket), not per-request rows - [ ] API credentials are stored as secrets, never committed, and never exposed to the SPA - [ ] The job is idempotent and tolerates gaps/retries without double-counting ## Notes Privacy-first: aggregate only, no per-request PII retention.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Directorium/Site#18

No description provided.

Rows
Columns