Community Dashboard

Usage and logs

Each service reports live counters, what it used each day, every call of the last 30 days, and the logs its calls wrote.

Every route here is for owners of the account.

Route Answers
GET /services/{owner}/{name}/usage Whether it is running, its memory and stored bytes, and each resource's total since its first deploy and rate over the UTC day so far.
GET /services/{owner}/{name}/meters Each of the last 30 days: calls, instructions, peak memory, rows read and written, bytes proxied, logged and stored.
GET /services/{owner}/{name}/billing?month=YYYY-MM Each day's cost in a month, and its total per resource.
GET /services/{owner}/{name}/calls Each call of the last 30 days, newest first.
GET /services/{owner}/{name}/logs Its logs, oldest first.
GET /orgs/{org}/meters, GET /users/{user}/meters Each of the account's services, each of the last 30 days.

Calls

  • Each call has its caller, outcome (done, failed, denied or refused), duration, what it used, its logs and its cost.
  • Filter with tool, outcome, since and until, and page with page and limit (100 by default, at most 1,000). The answer carries Link and X-Total-Count.
  • Each call's own response carries what it used in the Berm-Meter header.

Logs

  • A log belongs to the call that wrote it.
  • A log is at most 4 KiB and is kept 30 days.
  • Filter with topic, call and after.