Skip to content

Open Observability Results Standard (OORS)

The Open Observability Results Standard (OORS) is a lightweight, tool-agnostic format for exchanging data quality and data observability results.

An OORS message reports the outcomes of checks and metrics — pass/fail, measured values, threshold breaches — optionally linked to the data contract (ODCS/ODPS) that specified them. It deliberately does not carry raw metrics, traces, or logs.

WORK IN PROGRESS — NOT READY FOR PRODUCTION

OORS is a draft standard (v0.8.1), published early so the community can see it and shape it. It is not a released standard. Expect breaking changes in every version until v1.0.0, and incomplete areas. Do not build production systems against it.

Table of Contents

  • Fundamentals — the message envelope (apiVersion, kind, id, observedAt) plus the source and optional contract objects.
  • Results — the structure of an individual observation (check or metric).
  • Run Lifecycle — terminal by default, progressive by choice: the optional run object for long-running executions.
  • Custom & Other Properties — extending OORS with customProperties.
  • Tags — lightweight, free-form classification labels for the message and its results.
  • Variables — ${VAR_NAME} interpolation for environment-specific values, resolved at runtime by tooling.
  • Examples — complete OORS messages.

Design goals

  • Lightweight — a flat, concise structure; easy to print, log, send over HTTP, or push to a queue.
  • Tool-agnostic — can wrap results from OpenTelemetry, vendor tools, ETL pipelines, custom applications, or ad-hoc scripts.
  • Contract-aware — optional, first-class linkage to ODCS/ODPS IDs so data products can expose their health consistently.
  • Result-centric — carries only the outcomes of checks (pass/fail, measured values, breaches), not raw metrics or traces.

OORS is defined by RFC-0018, approved by the TSC on 2026-10-14, and is part of the Bitol family of standards, alongside ODCS and ODPS.