STARE OPSThe Kansas City Stare — operators only
STARE OPSwire console
Monitor
Overview Wire sources Stare analytics Stories Storage
Coverage
Editor's desk Newsroom Day Book Futures Crime monitor Coverage study KCPD data Crime Index Judiciary
Controls
Intel / AIIS Sources Publishing Engine
kcstare.com ↗

Stare analytics

Page views per day

Table view (requests · page views · uniques · threats)

Wire engine — worker health

The worker that aggregates the wire, serves the site's data, and answers this console. Cloudflare's free plan gives each invocation a fixed CPU budget; exceededResources means the budget ran out mid-request — the request died. Counts here are exact (invocation analytics, not sampled).

Where readers come from — our own counters

First-party, per /privacy: original Stare stories report a view and the host name only of the site that sent the reader, to our own worker. No third party involved, nothing identifies a person. Wire headlines and section pages are not counted here. Per-story detail lives in Stories.

Browser-measured readers (RUM)

off by policy

Human · computer · AI

Two instruments, strongest first. Verified bots (last 24h) is Cloudflare's own cryptographically verified taxonomy — a crawler on this list proved who it is, and "AI Crawler" vs "Search Engine Crawler" is Cloudflare's word, not a name-guess. Everything outside that list is unverified: humans plus anything lying about its user agent. The browser-family split below covers the whole selected range but classifies by name only. The strongest human evidence on this page is none of these — it is the first-party story counters above, which require a real browser to run our JavaScript and stay on the page.

Verified bots — Cloudflare-attested, last 24h
Browser families — name-classified, selected range

What was requested — last 24h

sampled · always 24h
Pages read
Probes, scrapers & infrastructure (the rest of the record)

Requests for paths that are not pages — asset files, feed pulls, and attack probes (a WordPress-install probe on an Astro site is a burglar checking a door this house does not have).

Who is asking — user agents

sampled · always 24h

Where readers are

Security — what the edge stopped

WAF events · last 24h

How to read this page: three instruments, three truths. Edge analytics (page views, bots, geo, security) see every request including non-JS crawlers; the 24h tables and the verified-bot split are Cloudflare's sampled adaptive dataset, daily and hourly totals are exact. Ranges run 1–30 days — the Workers dataset refuses anything wider than ~32 days, and the site is weeks old anyway. Our own story counters are exact and first-party but cover original stories only, and their per-day history keeps 60 days; browsers that have opened this console are excluded from them. Worker health is exact invocation accounting. The edge cannot see referrers on this plan (Free Website, checked 2026-08-26), and a scraper that lies about its user agent shows up as a browser — the verified-bot card is the antidote, listing only bots that proved who they are. No cookies, no visitor identifiers anywhere — aggregate only.