OrdinateDB

Documentation

product Pre-releaseunwritten sections are marked
GET/v1/calc/rules/{rule_id}/trace

Read calculation evaluation trace

operation ID: get_v1_calc_rules_by_rule_id_trace

Overview

Read calculation evaluation trace. The calculation API repairs historical derived data and explains how calculated values were produced.

When to use it

  • Use it when an application needs to read calculation evaluation trace.
  • Use it when an engineer is validating derived data, diagnosing a rule, or repairing a historical calculation window.

Quick example

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

cURL

curl --request GET \
  --url "$ORDINATE_URL/v1/calc/rules/00000000-0000-4000-8000-000000000001/trace?asset_id=00000000-0000-4000-8000-000000000001&start_ns=0&end_ns=0" \
  --header "Authorization: Bearer $ORDINATE_TOKEN"

Expected output · 200

Recorded evaluations

Example 200 output

{
  "evaluations": [
    {
      "asset_id": "00000000-0000-4000-8000-000000000001",
      "output_series": "00000000-0000-4000-8000-000000000001",
      "window": {
        "start_ns": 0,
        "end_ns": 0
      },
      "eval_instant_ns": 0,
      "rule_version": 0,
      "trigger": "string",
      "outcome": "string",
      "value": {},
      "quality": 0,
      "reason": "string",
      "provisional": false,
      "computed_at_ns": 0,
      "inputs": {}
    }
  ]
}

The cURL request supplies the documented path and query values and asks OrdinateDB to read calculation evaluation trace. The documented 200 response is recorded evaluations.

How it works

Backfills are managed jobs, while lineage, status, and trace reads expose the inputs and evaluation state behind calculated series.

Reference

Required capability
read
Authorization scope
handler-resolved target

Parameters

NameInRequiredType and constraints
rule_idpathyes
stringformat: uuid
asset_idqueryyes
stringformat: uuid
start_nsqueryyes
integer

UTC Unix timestamp in nanoseconds

format: int64
end_nsqueryyes
integer

UTC Unix timestamp in nanoseconds

format: int64

Request body

This operation has no request body.

Responses

200Recorded evaluations

application/json

evaluationsarrayrequired

array

asset_idstringrequired
format: uuid
computed_at_nsintegerrequired

UTC Unix timestamp in nanoseconds

format: int64
eval_instant_nsintegerrequired

UTC Unix timestamp in nanoseconds

format: int64
inputsany ofrequired

Arbitrary JSON value

any of

option 1

object with arbitrary properties

option 2

array

any items

option 3

string

option 4

number

option 5

integer

option 6

boolean

option 7

null
outcomestringrequired
output_seriesstringrequired
format: uuid
provisionalbooleanrequired
qualityany ofrequired

any of

option 1

integerformat: int64

option 2

null
reasonany ofrequired

any of

option 1

string

option 2

null
rule_versionintegerrequired
format: int64
triggerstringrequired
valueany ofrequired

any of

option 1

any of

option 1

object with arbitrary properties

option 2

array

any items

option 3

string

option 4

number

option 5

integer

option 6

boolean

option 7

null

option 2

null
windowobjectrequired
unknown fields rejected
end_nsintegerrequired

UTC Unix timestamp in nanoseconds

format: int64
start_nsintegerrequired

UTC Unix timestamp in nanoseconds

format: int64
unknown fields rejected
unknown fields rejected
unknown fields rejected

Example 200 output

{
  "evaluations": [
    {
      "asset_id": "00000000-0000-4000-8000-000000000001",
      "output_series": "00000000-0000-4000-8000-000000000001",
      "window": {
        "start_ns": 0,
        "end_ns": 0
      },
      "eval_instant_ns": 0,
      "rule_version": 0,
      "trigger": "string",
      "outcome": "string",
      "value": {},
      "quality": 0,
      "reason": "string",
      "provisional": false,
      "computed_at_ns": 0,
      "inputs": {}
    }
  ]
}
401Authentication required

application/json

ErrorEnvelope
codestringrequired
correlation_idstringrequired
format: uuid
detailsobjectoptional
errorstringrequired

Example 401 output

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}
403read capability is not granted

application/json

ErrorEnvelope
codestringrequired
correlation_idstringrequired
format: uuid
detailsobjectoptional
errorstringrequired

Example 403 output

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}
503Model database is not configured or unavailable

application/json

ErrorEnvelope
codestringrequired
correlation_idstringrequired
format: uuid
detailsobjectoptional
errorstringrequired

Example 503 output

{
  "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.

JavaScript

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

const response = await fetch(`${ordinateUrl}/v1/calc/rules/00000000-0000-4000-8000-000000000001/trace?asset_id=00000000-0000-4000-8000-000000000001&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);