Skip to content

nichedb-nightly: Traffic section (API demand, accounts, sign-in links) - #23

Merged
ralyodio merged 1 commit into
mainfrom
nichedb-nightly-traffic
Oct 16, 2026
Merged

ralyodio merged 1 commit into
mainfrom
nichedb-nightly-traffic

Conversation

@ralyodio

Copy link
Copy Markdown
Contributor

Anthony asked (bot@ queue, 2026-10-16) why the NicheDB nightly is all zeros and how to get numbers.

  • New Traffic section from data nichedb already records: api_usage (the API rate limiter's hourly per-caller counter, 7-day retention) gives requests and distinct callers for 24h and 7d; private/proxy addresses are counted separately. Plus accounts, sign-in links sent vs used, API keys issued, feed alerts delivered.
  • The closing note adds that the traffic is real and unpaid.
  • ssh read timeout 5 → 10 min (a daytime reading took 4m47s).
  • Verified: the full stats script ran live in nichedbdev-app-1 (273,011 requests / 193,264 addresses in 24h); rendered with --from-json; an old-shape JSON without the new keys still renders.

🤖 Generated with Claude Code

Anthony (bot@ queue, 2026-10-16): "can we track anything here? its all
zeros?". The money lines are zero because nothing has been bought, but the
API rate limiter's hourly counter (api_usage) already records every /api
request per caller: ~270K requests a day from ~190K addresses. The report now
shows that (internal proxy addresses counted apart), plus accounts, sign-in
links sent vs used, API keys and feed alerts delivered, and the closing note
says the traffic is real and unpaid. The ssh read timeout goes to 10 min: the
whole reading took 4m47s in the daytime against a 5 min limit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ralyodio
ralyodio merged commit 824263f into main Oct 16, 2026
4 checks passed
@ralyodio
ralyodio deleted the nichedb-nightly-traffic branch October 16, 2026 10:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant