What it does
GET /admin/db/capacity returns a capacity plan built from live server state: records, index size, host storage, memory and CPU, request and write rates, and realtime consumers. Every value carries a provenance tag. Forecasts come from an explicit growth assumption, and a projected breach of a limit you configure is flagged.
How it works
An administrator calls the route, optionally with query parameters: project (limit the record counts to one project), growth rate per period, number of periods, growth model (compound or linear), period unit (day, week, month, quarter or year), embedding dimension, storage price per gigabyte-month, and optional ceilings for records, consumers and retrieval rate.
Measured values come from live state: record and kind counts from the engine, the size of the vector index, storage, memory and CPU from the hardware probe, request and write rates from counters divided by uptime, and the number of realtime subscribers. Configured values are the limits and prices you supply, and the embedding dimension. Projected values are computed from a measured baseline and a stated growth assumption, and cannot be constructed without that assumption.
Model token rate, disk I/O and network have no source wired. They come back as an explicit unavailable hook and never as an invented number. When a projected value crosses a configured ceiling inside the horizon, the plan reports a breach. The plan id is a hash of the inputs and assumptions without the clock, so the same inputs give the same id and a changed assumption changes it.
If the engine is fenced after a recovery fault, the request is refused with the typed 503 instead of publishing a measured zero for records.
Where you reach it
- HTTP
GET /admin/db/capacity?project=&growth=&periods=&model=&period=&embedding_dim=&price_per_gb=&record_limit=&consumer_limit=&qps_limit=
Limits
- Rates are averages over the metrics window or since process start, not peaks.
- Model token rate, disk I/O and network are not measured.
- It is a report. Nothing acts on it, and it does not resize anything.
- It describes one instance. Plan a fleet by combining the reports.
Evidence
- On this siteDocumentation hub: operations
- TestsCovered in the engine repository by 11 honesty tests (every value typed, no projection posing as a measurement, hooks not fabricated, deterministic plan id), 9 projection tests with known answers, 3 tests that read a real engine, and 4 server-side builder tests including refusal while the engine is fenced
Test coverage is listed as present in the engine repository at this edition. This page does not report test results.
KynetraDB is in private preview
Request a preview to try this against your own workload.