Service Dependency Graph — Derived from the Trace Set (json)
The service map you get by aggregating the trace fixtures in this category — five service nodes and the edges between them with call counts and latency percentiles, including the messaging edge that exists only because of a span link. Ground truth for a service-graph processor.
{
"generatedFrom": [
"4bf92f3577b34da6a3ce929d0e0e4736",
"7f8a9b0c1d2e3f405162738495a6b7c8"
],
"window": {
"start": "2026-03-17T09:14:32.850Z",
"end": "2026-03-17T10:14:32.850Z"
},
"nodes": [
{
"id": "checkout-api",
"type": "service",
"namespace": "shop",
"version": "1.14.2",
"instances": 1,
"host": "node-a1"
},
{
"id": "cart-api",
"type": "service",
"namespace": "shop",
"version": "0.9.7",
"instances": 1,
"host": "node-a2"
},
{
"id": "inventory-api",
"type": "service",
"namespace": "shop",
"version": "2.3.0",
"instances": 1,
"host": "node-b1"
},
{
"id": "payments-api",
"type": "service",
"namespace": "shop",
"version": "3.1.4",
"instances": 1,
"host": "node-b2"
},
{
"id": "notifier",
"type": "service",
"namespace": "shop",
"version": "0.4.11",
"instances": 1,
"host": "node-c1"
}Specifications
- Nodes
- 5
- Edges
- 4
- Derived From Traces
- 2
- Has Messaging Edge
- true
- Window Minutes
- 60
Testing contract
Reference control- Scenario
- Run a service-graph processor over the trace fixtures and compare its output to this file.
- Expected result
- It produces the same 5 nodes and edge set, including the checkout-api to notifier edge that is only discoverable through the span link rather than through parentage.
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
“Service Dependency Graph — Derived from the Trace Set (json)” is a deterministic Novus Examples fixture for Observability, Graph data, 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: 5 nodes · 4 edges. 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("service-dependency-graph.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- jsonOTLP Trace — Span Links from a Batch Consumer (json)The consumer half of the checkout flow, in its own trace. Its root CONSUMER span carries a link — not a parent reference — back to the producer span in the checkout trace, which is how a batching consumer joins work produced elsewhere. A fixture for link resolution and cross-trace navigation.
- jsonFlamegraph Hierarchy — Nested name/value/children Tree (json)The folded CPU profile after aggregation into the nested name, value and children hierarchy that d3-flame-graph and most web viewers consume. Every node's value equals its own self time plus its children's, which is the invariant a converter must preserve.
- 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 — 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.
Generated by generation/observability.py. Free for any use, no attribution required — license.