Skip to content
Novus Examples
json4.6 KB

OTLP Trace — Stable HTTP Semantic Conventions (json)

The same HTTP server span written with the stable attribute names — http.request.method, url.path, http.response.status_code, client.address — and the route-templated span name the stable conventions require. The target state for a migration shim.

ObservabilityConversion testingMetadata testing
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": {
… 183 lines total — download for the full file.

Specifications

Spans
1
Attributes
11
Convention Era
stable HTTP (1.23+)
Span Name Style
POST /api/checkout
Has Http Route
true

Testing contract

Reference control
Scenario
Compare a migrated legacy span against this file field by field.
Expected result
The migrated span matches on all 11 attributes and on the route-templated name POST /api/checkout, which the legacy fixture cannot supply without an http.route source.

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 — Stable HTTP Semantic Conventions (json)” is a deterministic Novus Examples fixture for Observability, Conversion testing, Metadata 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 · 4,689 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-semconv-current.json") as f:
    data = json.load(f)
print(type(data), len(data))

Related files

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