Read stored rollup rows

Overview

Read stored rollup rows. Series-storage operations expose registered series, direct stored data, gap and chunk metadata, and lifecycle controls.

When to use it

• Use it when an application needs to read stored rollup rows.
• Use it when a diagnostic or maintenance tool needs storage-level series data instead of model-resolved attributes.

Quick example

Set the base URL and replace generated identifiers or credentials with values from your installation.

curl --request GET \
  --url "$ORDINATE_URL/v1/series/00000000-0000-4000-8000-000000000001/rollups?tier=1h&start_ns=0&end_ns=0" \
  --header "Authorization: Bearer $ORDINATE_TOKEN"

{
  "rows": [
    {
      "window_start_ns": 0,
      "count": 0,
      "min": 0,
      "max": 0,
      "sum": 0,
      "tw_sum_linear": 0,
      "tw_sum_stepped": 0,
      "first": 0,
      "last": 0,
      "good_time_ns": 0,
      "percent_good": 0,
      "finalised_at_ns": 0
    }
  ]
}

The cURL request supplies the documented path and query values and asks OrdinateDB to read stored rollup rows. The documented 200 response is raw rollup rows; percent_good is the stored 0-1 fraction.

How it works

Reference

Required capability

read

Authorization scope

owning asset of series path parameter `uuid`, or staging-root

{
  "rows": [
    {
      "window_start_ns": 0,
      "count": 0,
      "min": 0,
      "max": 0,
      "sum": 0,
      "tw_sum_linear": 0,
      "tw_sum_stepped": 0,
      "first": 0,
      "last": 0,
      "good_time_ns": 0,
      "percent_good": 0,
      "finalised_at_ns": 0
    }
  ]
}

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}

Code examples

These examples are generated from the source contract. Replace the base URL, credentials, identifiers, and minimal generated values for your instance.

const ordinateUrl = "http://localhost:8080";
const token = "<bearer-token>";

const response = await fetch(`${ordinateUrl}/v1/series/00000000-0000-4000-8000-000000000001/rollups?tier=1h&start_ns=0&end_ns=0`, {
  method: "GET",
  headers: {
    Authorization: `Bearer ${token}`
  }
});

if (!response.ok) {
  throw new Error(`OrdinateDB returned ${response.status}: ${await response.text()}`);
}

const data = await response.json();
console.log(data);