Ask the database what's hot

Something is hammering the database. On a managed platform you open the provider's metrics page and try to correlate graphs. Here you curl the service: GET /api/v1/sqlite/health/cache returns cache size against capacity, hits, misses, evictions: and hotKeys, the actual keys taking the most traffic right now. session:890ab… at the top of that list at 9am tells you exactly which code path went hot.

The full /health endpoint adds process memory and file-descriptor counts, so your readiness probe and your capacity question share one scrape. No agent installed in the container, no metrics pipeline, no dashboard seat. The database answers "what's hot" the way it answers everything else: over HTTP, in JSON, to whoever asks.

Observability is an endpoint the database was born with.