OBSERVABILITY // EDGE & SERVERLESS

CLOUDFLARE
SAYS 500.
ZERO LOGS.

Know your Worker broke, why it broke, and what it cost you — before your users tell you. Capture console.error and crashes automatically.

// Works with Cloudflare Workers, Next.js, Vercel, Hono & more — one SDK, one dashboard

$ npm install @flarelog/sdk

// Free up to 10k logs/mo // No card required

LIVE_FEED.EXE
ACTIVE
INFOGET /api/users - 200 OK (24ms)
WARNKV read latency high: 145ms
INFOPOST /webhooks/stripe - 200 OK (89ms)
ERRORUncaught TypeError: Cannot read properties of undefined
INFOWorker tail connected successfully
01COST BURN MONITOR

Catch a $500 KV loop before billing sees it.

Cloudflare's cost metrics lag 15–60 minutes. A misconfigured loop can rack up KV writes, R2 Class A operations, or D1 row reads long before the bill appears. FlareLog measures CPU, subrequests, and duration in real time on every execution.

1

Per-Request Cost Estimation

Immediately calculates costs from incoming Tail Worker CPU & subrequest metrics.

2

Instant Alert Triggering

Dispatches webhooks to Slack or Discord when cost speeds past defined budgets.

3

Granular Allocation Breakdown

Filter by Worker name, route, HTTP status, or deployment tag to narrow down leaks.

Cost per request+$482 vs average
$0.025$0.015$0.005$0.000
Danger Budget Zone
Alert Triggered
Request cost exceeded $0.005 budget threshold by 24x.
02FLYING BLIND

What Cloudflare can't tell you.

Cloudflare's native observability got better in 2025. It still can't tell you when your Worker died silently, when a KV loop is burning money, or why a 500 happened with zero logs. FlareLog can.

01

HTTP 500, zero logs

When a Worker times out, exceeds CPU, or crashes before logging, your SDK never fires. The Tail Worker still captures the failure because it runs after the producer code.

02

Debug blind from day one

No manual boilerplate needed. The FlareLog SDK intercepts console.error and unhandled exceptions automatically, capturing accurate execution context.

03

7-day amnesia

Cloudflare keeps logs for 7 days. If a customer reports an edge incident from last week, you're out of luck. FlareLog keeps up to 90 days on Pro tiers to keep incidents searchable.

03HOW IT WORKS

Dual-Layer Edge Observability

Combine runtime code errors from our SDK layer with underlying compute metrics from Cloudflare's Tail Consumer. No gaps, no blindspots.

// LAYER_01ACTIVE_PRODUCER

SDK Layer

Embedded inside your standard worker script. Dispatches captured exception payloads and developer info log commands.

console.error / logger.info()
// LAYER_02CONSUMER_TAIL

Tail Worker Layer

Listens out-of-band at the edge interface. Measures the final compute cost, wall CPU, memory limits, and handles silent timeouts.

CPU + class_a_ops + class_b_ops
CONVERGED INSIGHTS

Unified FlareLog Dashboard

04LIVE CONSOLE

Every crash, fully inspectable.

Correlate business log entries with their exact underlying tail statistics inside an integrated debugging pane.

ACTIVE_STREAM_CONSOLE
LIVE_FEED
[WARN]
Database connection delay: 450ms
1m ago
[INFO]
GET /projects/new - 200
3m ago
[ERROR]
D1 query timeout after 5000ms
4m ago
[INFO]
KV hit ratio: 92% (last 5m)
6m ago
[WARN]
CPU duration 480ms (limit 500ms)
8m ago
[INFO]
POST /webhooks/stripe - 200
12m ago
[ERROR]
Queue consumer exhausted retries (3/3)
15m ago
// INCIDENT_DETAILSWARN
Message

Database connection delay: 450ms

Source Service

db.d1

Unique Trace ID

tr_218cd98b8df116aa

05QUICK INTEGRATION

Get running in under 2 minutes.

Install the lightweight SDK package or map our tail listener worker script globally.

STAY OBSERVANT

KNOW WHEN IT BROKE.

Drop in our lightweight SDK & edge listener scripts in minutes. Stop guessing and capture silent uncaught failures before they spike your invoice.