OTLP Trace — Orphan Span with a Missing Parent (json)
The checkout trace with one intermediate span dropped, as happens when an exporter's queue overflows. Three spans now reference a parent that is not in the payload — a partial trace that a store must render rather than reject.
{
"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": {Specifications
- Spans
- 12
- Missing Span Id
- 8192a3b4c5d6e7f8
- Orphaned Subtrees
- 1
- Spans Referencing Missing Parent
- 1
- Detached Subtree Spans
- 2
- Cause
- dropped span in a partial export
Testing contract
Expected to recover- Scenario
- Ingest the partial trace and render whatever can be rendered.
- Expected result
- 12 spans are stored and one references the absent parent 8192a3b4c5d6e7f8, leaving a two-span subtree detached; the viewer shows the broken subtree rather than discarding the whole trace.
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 — Orphan Span with a Missing Parent (json)” is a deterministic Novus Examples fixture for Observability, Error handling, JSON parsing. 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 · 27,291 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-orphan-span.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- jsonOTLP Trace — ERROR Status and Exception Event (json)A failed checkout: an upstream payment timeout sets ERROR status on four spans up the chain and attaches an exception event whose exception.stacktrace attribute holds a real multi-line Python traceback with embedded newlines. The fixture for error grouping, status propagation and multi-line attribute rendering.
- jsonOTLP Trace — Truncated Mid-Object, Intentionally Corrupt (json)An OTLP/JSON export cut off in the middle of an object, the way a file sink looks when the collector is killed mid-write. This file is intentionally corrupt and small: it exists so an ingestion path can be tested for a clean parse error with a byte offset instead of a hang or a half-committed batch.
- jsonJaeger JSON Trace — Same 13-Span Checkout (json)The checkout trace in the Jaeger query-API shape — a data array holding one trace, spans carrying microsecond startTime and duration, CHILD_OF references, typed tags and a per-service processes map. The same span tree as the OTLP and Zipkin twins, so a converter can be scored exactly.
- jsonOTLP Trace — 48-Span Linear Chain (json)A single-service trace 48 levels deep — a recursive GraphQL-style resolver where every span is the child of the one before it. A depth fixture for waterfall renderers, tree-layout code and any parser that recurses over parentage.
- jsonOTLP Trace — 60-Way Parallel Fan-Out (json)One root span with 60 overlapping children — a scatter-gather query across database shards. The counterpart to the deep-chain fixture: shallow but very wide, which is what breaks waterfall layouts that assume spans do not overlap in time.
- jsonOTLP 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.
Generated by generation/observability.py. Free for any use, no attribution required — license.