This document tracks the history and evolution of the Open Observability Results Standard.
v0.8.1 - DRAFT
- Adds optional
results[].target.filter— the condition (a partition or a where clause) that restricted the observed data to a subset of the resource. Without it, a result that covers one partition reads as covering the whole resource. Non-breaking: the field is optional. - Adds optional
results[].measure.rowCountandresults[].measure.failedRowCount— the number of rows evaluated and the number that did not meet the expectation, so consumers can compute the share of failing rows across tools, independent of the metric invalue. Non-breaking: the fields are optional. - Adds optional
run.startedAt— when the run started, so its duration is not lost. Non-breaking: the field is optional. - Extends
results[].statuswithunknown— the producer cannot tell the outcome, e.g. it relays a result from another tool whose status it does not recognize. Distinct fromerror(the evaluation broke and needs fixing); likeskip, it is counted neither as a pass nor as a failure. Non-breaking — this widens an enum. See Status values. - Adds optional top-level
status— the overall outcome of the document, with the same values asresults[].status, so consumers and quality gates can read one field instead of aggregating the results. When present, it SHOULD equal the outcome derived fromresults(the first oferror,fail,warn,pass,skipthat occurs, elseunknown); consumers SHOULD derive it with the same rule when it is absent. See Overall status. Non-breaking: the field is optional. - Allows an empty
resultsarray, for runs that made no observations (no checks defined, or all filtered out), instead of forcing producers to invent a placeholder result.resultsitself stays required. Non-breaking — this relaxes a constraint. - Recommends the ODCS library metric names (
rowCount,nullValues,missingValues,invalidValues,duplicateValues) formeasure.metric. The duplicate-row examples now useduplicateValuesinstead ofrowCount. - Default
apiVersionraised tov0.8.1. The v0.8.0 schema is unchanged. - The
fullexample gainstarget.filter,measure.rowCount,measure.failedRowCount,run.startedAtand the top-levelstatus; thestatusesexample gains anunknownresult.
v0.8.0 - DRAFT
- Approves RFC-0018 — Open Observability Results Standard, the founding RFC, approved by the TSC on 2026-10-14. OORS is no longer an implementation of an open draft: it is now the formal consequence of an approved RFC.
- Adds optional
contract.server— the identifier of the server, as defined in the referenced contract (e.g., theservername in the ODCSserverssection), against which the observations were made. A contract can be served on multiple servers (e.g.,production,dev); this field records which one the results apply to. Non-breaking: the field is optional. Recreates the contribution made in #8 by @jochenchrist on top of v0.8.0. - Adds
tags— the shared Bitol structure for free-form classification labels (an array of strings), available at the top level and on each result. See the new Tags page. Non-breaking: the field is optional. - Extends
results[].statusto the five outcomes the RFC defines:pass,fail,warn(executed, breached a soft/warning threshold),error(could not be evaluated — verdict unknown; e.g. the query failed or the source was unreachable) andskip(intentionally not run). The schema previously permitted onlypassandfail.erroris deliberately distinct fromfail: a failure is a known-bad verdict, anerroris the absence of a verdict and must not be counted as a failure. Non-breaking — this widens an enum. See Status values. - Documents
severityas orthogonal tostatus:statusis the runtime outcome,severityis the definition-time importance of the check. The two compose — acritical-severity check withstatus: erroris the loudest possible alert. - Default
apiVersionraised tov0.8.0. - New
statusesexample (YAML + JSON) exercising all five outcomes, and the first negative-test fixtures undertests/negative/— invalid documents the schema must reject — wired intoscripts/validate-examples.sh. - New Tags documentation page, mirroring the ODCS page; Custom & Other Properties restructured to align with ODCS. The
fullexample gainscontract.serverandtags.
v0.2.2 - DRAFT
- Renames
source.runIDtosource.runIdandcontract.contractIDtocontract.contractId, following the Bitol camel-case naming convention. Breaking:sourceandcontractsetadditionalProperties: false, so documents still usingrunIDorcontractIDno longer validate against the v0.2.2 schema. - Default
apiVersionraised tov0.2.2.
v0.2.1 - DRAFT
- Adds optional top-level
runobject — run lifecycle reporting: terminal by default, progressive by choice. A document withoutrun(every pre-v0.2.1 document) is terminal: the authoritative record of its run. Producers of long-running executions can opt in to interim snapshots withrun.state: running, plus optionalrun.sequence(monotonic ordering persource.runID) andrun.progress(current/total/unit).run.state: completed|abortedmarks a terminal document; a terminal document supersedes all interim documents sharing itssource.runID.source.runIDis required (schema-enforced) whenrun.stateisrunning.results[].statussemantics are unchanged — lifecycle is orthogonal to observation outcomes. See the new Run Lifecycle page. - Default
apiVersionraised tov0.2.1. - New
progressiveexample (YAML + JSON);fullexample extended with therunobject.
v0.2.0 - DRAFT
- Adds
customProperties— a list of key/value pairs (shared structure across the Bitol standards:property,value, optionaldescriptionandid) at the top level and on each result, for vendor- or organization-specific extensions. - Adds optional
vendorstring oncustomPropertiesitems, associating a custom property with a specific vendor, provider, or external system. SHOULD be a stable, lowercase identifier (^[a-z0-9][a-z0-9-]*$); not enforced, and tools MUST preserve unknown vendor values — RFC 0035, shared with ODCS v3.2.0 and ODPS v1.1.0 (slated for OORS v1.0.0). - Adds
relatesToon result objects — an optional reference to the element this result relates to in the linked contract (e.g., a path to a data quality rule or property in the referenced ODCS/ODPS contract). - Adds variable interpolation — any string value MAY contain
${VAR_NAME}references resolved at runtime by tooling, with the POSIX${VAR_NAME:-default}form for inline defaults. Tools MUST resolve references before use, MUST NOT silently substitute empty strings, and MUST preserve unresolved tokens verbatim on round-trip. No new section or field — RFC 0050, shared with ODCS v3.2.0 and ODPS v1.1.0 (slated for OORS v1.0.0). - Default
apiVersionraised tov0.2.0. - Documentation expanded to match the ODCS/ODPS structure: per-section pages with front matter, a table-of-contents landing page, and a Custom & Other Properties page.
v0.1.0 - DRAFT
Initial draft of the Open Observability Results Standard, based on RFC-0018.
- Top-level fundamentals:
apiVersion,kind(ObservabilityResults),id,observedAt. sourceobject:process(required),runID,vendor.- Optional
contractobject linking results to an ODCS/ODPS contract:contractID,standard,version. resultsarray (at least one) of result objects, each withid,type(check/metric),name,status(pass/fail), and optionalseverity,dimension,target(resourceType,resourceIdentifier),measure(metric,value,threshold,unit), andmessage.- JSON Schema (
oors-json-schema-v0.1.0.json) and example messages.