OriginChainDB
Database endpoints

Read query metrics

Read query completion counts and mean latency from the running process, without collecting query text.

GET /v1/tenants/{tenant}/query-metrics

Read query activity over a time windowMetrics belong to the running process and restart with it.
  1. Choose the time bucketsSet the window and bucket size.
  2. Read calls and failuresInspect counts and mean latency per bucket.
  3. Calculate rates carefullyUse observed_seconds; idle latency may be null.

Before you start

Use your database bearer token.

Connection setup

Use a tenant service credential or query administrator; supported windows are 60/60, 1440/600 and 10080/3600 minutes/bucket_seconds.

Path parameters

FieldTypeRequired
tenantstringRequired

Query parameters

FieldTypeRequired
minutesintegerRequired
bucket_secondsintegerRequired

Headers

FieldTypeRequiredDescription
x-oc-db-userstringOptionalActing database user (role, grant and row-policy checks). Send with x-oc-db-key.
x-oc-db-keystringOptionalAPI key of the x-oc-db-user user.

Read the result

Read calls, failed and mean_latency_ms per bucket. Divide by observed_seconds when calculating rates. The history belongs to the local process and restarts with it; idle latency can be null.

Response statuses

HTTP status reference
StatusWhat to do
200OK
400Correct the request before retrying.
401Check the credential and Authorization header.
402Check feature access or available credits.
403Check tenant access, roles and permissions.
422Correct the values or unsupported combination.
429Honor Retry-After when present; back off.
503Honor Retry-After when present; check write outcomes.
ยฉ 2026 Silicoyn Technologies Pvt Ltd