Prometheus HTTP API — query_range Matrix Response (json)
A Prometheus /api/v1/query_range response: three labelled series of 30 points each at a 60-second step, with sample values as JSON strings and timestamps as float seconds. The exact envelope a dashboard client has to unpack, including the string-typed values that break naive charting code.
{
"status": "success",
"data": {
"resultType": "matrix",
"result": [
{
"metric": {
"__name__": "http_request_duration_seconds",
"service": "checkout-api",
"route": "/api/checkout",
"quantile": "0.95",
"job": "checkout-api",
"instance": "192.0.2.11:9090"
},
"values": [
[
1773737132,
"0.166204"
],
[
1773737192,
"0.141441"
],
[
1773737252,
"0.136772"
],
[
1773737312,
"0.168444"
],
[
1773737372,
"0.127622"
],
[
1773737432,
"0.153412"
],
[
1773737492,
"0.154508"
],
[
1773737552,
"0.106735"
],
[
1773737612,
"0.126495"Specifications
- Result Type
- matrix
- Series
- 3
- Points Per Series
- 30
- Step Seconds
- 60
- Values As Strings
- true
- Seed
- 7301
- Window Minutes
- 30
Testing contract
Expected to pass- Scenario
- Parse the response and plot all three series on one axis.
- Expected result
- Three series of 30 points parse, each value converts from its JSON string to a float, and the timestamps are read as seconds rather than milliseconds.
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
“Prometheus HTTP API — query_range Matrix Response (json)” is a deterministic Novus Examples fixture for Observability, JSON parsing, Time-series data. 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: seed 7301. 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("prometheus-api-query-range.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- promOpenMetrics — Histogram Exemplars Linking to the Trace Fixtures (prom)Histogram buckets carrying exemplars whose trace_id and span_id resolve against the OTLP trace fixtures in this category — the exact-to-example link that turns a latency spike on a graph into a specific request. Five exemplars, each with its own observed value and timestamp.
- jsonOTLP Metrics — Exemplars with Trace and Span IDs (json)An OTLP histogram carrying two exemplars, each with the trace and span ID of a request that landed in that bucket — including the 2.0031-second outlier that corresponds to the failed payment in the error-trace fixture. The metrics-to-traces jump, with a resolvable target.
- jsonOTLP Metrics — Monotonic Sum and Gauge Data Points (json)An OTLP metrics export with a monotonic cumulative sum and two gauges, showing the parts of the wire format that trip parsers: int data points serialised as JSON strings, UCUM unit annotations like {request} and By, and the start timestamp that makes a counter reset detectable.
- promOpenMetrics — Full Document with UNIT, info and stateset (prom)A complete OpenMetrics document — the _total and _created series a counter really has, UNIT metadata, an info metric carrying build metadata and a stateset with exactly one active state — terminated by the mandatory # EOF. This is what the exposition format became once it was standardised.
- jsonOTLP Metrics — Base-2 Exponential Histogram (json)An exponential histogram at scale 3 — eight buckets per power of two — with a negative offset, a zero bucket and its threshold. Bucket i covers (base^(offset+i), base^(offset+i+1)], and getting that indexing wrong silently shifts every percentile, which is what this fixture is for.
- jsonOTLP Metrics — Counter Reset on Process Restart (json)A monotonic counter that drops from 94,880 to 1,120 when its process restarts, with startTimeUnixNano changing at exactly that point to mark the reset. Rate calculations that subtract consecutive values without checking the start timestamp produce a large negative rate here.
Generated by generation/observability.py. Free for any use, no attribution required — license.