Jaeger 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.
{
"data": [
{
"traceID": "4bf92f3577b34da6a3ce929d0e0e4736",
"spans": [
{
"traceID": "4bf92f3577b34da6a3ce929d0e0e4736",
"spanID": "00f067aa0ba902b7",
"operationName": "POST /api/checkout",
"references": [],
"startTime": 1773738872850000,
"duration": 148200,
"tags": [
{
"key": "http.request.method",
"type": "string",
"value": "POST"
},
{
"key": "url.path",
"type": "string",
"value": "/api/checkout"
},
{
"key": "url.scheme",
"type": "string",
"value": "https"
},
{
"key": "http.response.status_code",
"type": "int64",
"value": 201
},
{
"key": "http.route",
"type": "string",
"value": "/api/checkout"
},
{
"key": "server.address",
"type": "string",
"value": "shop.example.com"
},
{
"key": "client.address",
"type": "string",
"value": "203.0.113.42"
},
{
"key": "user_agent.original",Specifications
- Shape
- Jaeger query API /api/traces response
- Spans
- 13
- Processes
- 5
- Time Unit
- microseconds
- References
- CHILD_OF
- Trace Id
- 4bf92f3577b34da6a3ce929d0e0e4736
Testing contract
Reference control- Scenario
- Convert the OTLP twin to Jaeger and diff the result against this file.
- Expected result
- Span IDs, parent references, operation names, microsecond timings and the five-process map all match; typed tags keep int64/bool types that Zipkin would flatten to strings.
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
“Jaeger JSON Trace — Same 13-Span Checkout (json)” is a deterministic Novus Examples fixture for Observability, JSON parsing, Conversion testing. 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 · 22,766 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("jaeger-trace-checkout.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- jsonOTLP Trace — Stock proto3 JSON Encoding (base64 IDs) (json)The same 13-span trace serialised the way a stock proto3 JSON marshaller writes it: trace and span IDs base64-encoded and span kind and status as enum names rather than numbers. Paired with the hex/numeric OTLP/JSON twin so a receiver can be tested against both encodings of one payload.
- jsonOTLP Metrics — Summary with Client-Side Quantiles (json)The OTLP summary type — quantiles computed on the client, kept only for translating legacy Prometheus summaries. It carries the same four quantiles as the Prometheus summary fixture, and like that one it cannot be re-aggregated across instances without producing a wrong number.
- 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 — AnyValue Attribute Type Matrix (json)One span carrying every OTLP AnyValue kind — string (plain, Unicode, multi-line, empty), int64 encoded as a JSON string, double, bool, array, nested kvlist and base64 bytes. Includes an integer above 2^53 to catch decoders that route int64 through a JavaScript number.
- jsonOTLP Trace — Clock Skew, Child Starts Before Its Parent (json)Two hosts whose clocks disagree by 12 ms, so a server span appears to start before the client span that called it. Nothing in the payload is malformed — this is the most common real cause of a negative-latency gap in a waterfall, and viewers must show it rather than crash or silently reorder.
Generated by generation/observability.py. Free for any use, no attribution required — license.