json6.2 KB

OTLP Trace — All-Zero Trace and Span IDs, Intentionally Invalid (json)

A trace whose trace ID and root span ID are all zeroes — the value an uninitialised context produces. Intentionally invalid: the specification defines all-zero IDs as invalid, so a conformant receiver must reject the spans instead of creating a permanent bucket that every broken service writes into.

Observability Schema validation Error handling

Preview — first 50 linesjson

{
  "resourceSpans": [
    {
      "resource": {
        "attributes": [
          {
            "key": "service.name",
            "value": {
              "stringValue": "checkout-api"
            }
          },
          {
            "key": "service.namespace",
            "value": {
              "stringValue": "shop"
            }
          },
          {
            "key": "service.version",
            "value": {
              "stringValue": "1.14.2"
            }
          },
          {
            "key": "service.instance.id",
            "value": {
              "stringValue": "checkout-api-7d9f4c-2xk"
            }
          },
          {
            "key": "deployment.environment.name",
            "value": {
              "stringValue": "staging"
            }
          },
          {
            "key": "host.name",
            "value": {
              "stringValue": "node-a1"
            }
          },
          {
            "key": "host.ip",
            "value": {
              "stringValue": "192.0.2.11"
            }
          },
          {
            "key": "cloud.region",
            "value": {

… 239 lines total — download for the full file.

Specifications

Spans: 2
Trace Id: 00000000000000000000000000000000
Root Span Id: 0000000000000000
Intentionally Invalid: true
Rule: all-zero IDs are invalid and must be rejected

Testing contract

Expected to fail

Scenario: Submit the payload to an OTLP receiver or trace store.
Expected result: Both spans are rejected as invalid rather than stored under the all-zero trace ID, which would otherwise collect every uninstrumented request in the system.

What is a .json file?

JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.

How to use this file

Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.

How to use this file for testing

“OTLP Trace — All-Zero Trace and Span IDs, Intentionally Invalid (json)” is a deterministic Novus Examples fixture for Observability, Schema validation, Error handling. Structured and plain-text telemetry with known timestamps, levels, request identifiers, and error states for testing log ingestion, correlation, dashboards, and alert pipelines.

Documented properties for this file: JSON · 6,398 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.

Telemetry fixtures use fixed trace IDs, span IDs, and timestamps so ingestion is reproducible run to run. Point your collector, parser, or query layer at the file and assert the documented span tree, metric families, or severity mix; service and host names are invented.

Code examples

import json

with open("otlp-trace-zero-ids.json") as f:
    data = json.load(f)
print(type(data), len(data))

Generated by generation/observability.py. Free for any use, no attribution required — license.