Diagnose billing and usage
Find the first divergence from accepted route through gateway decision, backend report, aggregation, and plan settlement.
Find the first divergence from accepted route through gateway decision, backend report, aggregation, and plan settlement.
The first divergent boundary is identified with request, environment, plan, meter, subscription, and period evidence before any corrective write.
farthershore business status acme --format json
farthershore business routes acme --env production --format json
farthershore business contract acme --env production --format json
farthershore plan list acme --format json
Record the release, environment, route, meter, plan version, and billing period. Do not compare production charges with preview traffic.
farthershore analytics log acme --range 1h --domain usage --limit 100 --format json
farthershore analytics timeseries acme --range 24h --domain usage --format json
farthershore usage summary acme --format json
For one request id, compare:
meterRoutes binding in the served release.report() — meter, measure keys, dimension values.Common first divergences are an unmatched route, an unbound meter, a measure or dimension key the release's schema rejects, a report retried outside its original request context, the wrong environment, or a unit mismatch. Usage is rated under the release it was admitted with — a catalog change after the fact never explains an old charge.
Use historical replay only as a preview:
farthershore workflow-control replay acme \
--period-start 2026-08-01T00:00:00Z \
--period-end 2026-09-01T00:00:00Z \
--format json
The command does not charge or mutate provider state. Do not edit invoices or replay real usage until the first divergence is understood. Fix contract or backend code in preview; if the whole request chain is correct but settlement is not, preserve request ids, decision ids, subscription id, period bounds, and release for support.
See Observe usage and billing and Ledger & settlement.
Re-run one controlled request in the same environment and require matching route, decision, reported dimensions, aggregated quantity, and plan version. Do not compare preview traffic with production settlement.
Fix the first repository- or backend-owned divergence in preview and push a new commit. A historical replay command is preview-only. If settlement remains wrong after the request chain matches, stop and preserve ids and period bounds for escalation.
Trace one usage or billing mismatch from accepted route through gateway
decision, backend report, aggregation, and active plan settlement. Identify the
first divergence and report evidence; do not mutate billing state.